I\'m using pandas on a web server (apache + modwsgi + django) and have an hard-to-reproduce bug which now I discovered is caused by pandas not being thread-safe
see caveat in the docs here: http://pandas.pydata.org/pandas-docs/dev/gotchas.html#thread-safety
pandas is not thread safe because the underlying copy mechanism is not. Numpy I believe has an atomic copy operation, but pandas has a layer above this.
Copy is the basis of pandas operations (as most operations generate a new object to return to the user)
It is not trivial to fix this and would come with a pretty heavy perf cost so would need a bit of work to deal with this properly.
Easiest is simply not to share objects across threads or lock them on usage.