Re: [matplotlib-devel] Multithreading problem with print_png and font object?

[Darren D. <dsd...@gm...>]

On Thu, Mar 26, 2009 at 8:10 PM, Eric Firing <ef...@ha...> wrote:

> Karen Tracey wrote:
> > I originally posted this to the user's list but got no response there.
> > As I think there's a bug in matplotlib here, I'm re-trying on the
> > development list.  Here's what I sent to -users back on Mar 13:
>
>
>
> Karen,
>
> (I saw your question to the users group, and was hoping someone more
> knowledgeable than myself about threading problems would reply to you.)
>
>
> http://www.mail-archive.com/mat...@li.../msg06152.html
>
> I don't think there has been any progress on this question since it came
> up a year ago in the above thread.  Evidently it is something that needs
> more attention.  I would say that you have found a bug, and there are
> probably many more.  There are global objects outside the pyplot
> interface; maybe they provide opportunities for threads to trip over
> each other. A reasonable goal would be to have matplotlib be thread-safe
> at least when the pure OO interface is used, and possibly with some
> additional restrictions such as "don't mess with rcParams when more than
> one thread might be running".


It might not be too much trouble to protect RcParams and its data, although
I dont know how disruptive it would be to the mpl codebase and to users for
rcParams to begin returning copies of things like font lists.

Darren