Re: [Matplotlib-users] FW: traceback when import matplotlib.pyplot twice

[Mark J. <mja...@es...>]

When I replaced the file I got the 1st error below.   As you had pointed out earlier… this is strange.  It only occurs when you run it more than once… strange indeed… it is like a manager is being created and deleted but perhaps the reference hasn’t… so you get a no-op on the subsequent import.. but are then left with a manager that is None….?? Thanks for the tip BTW… I replaced all my None comparisons to “is” and “is not”.   I went ahead and added the comparisons to your changes and it works… but now you need to assure that you do not gc.collect unless you had at least one Non-None manager or else you get the 2nd traceback.  The code that works on my end is the last image… not sure if it passes your regression tests..??..??



Thanks so much for all of your help… please let me know if there is anything else I can do to help.



MJ





[cid:image001.png@01CFE881.FB6CCAF0]



[cid:image002.png@01CFE888.2A514840]



[cid:image003.png@01CFE888.2A514840]

-----Original Message-----

From: Thomas Caswell [mailto:tca...@gm...]

Sent: Saturday, October 11, 2014 2:18 PM

To: Phil Elson

Cc: Mark Janikas; Benjamin Root; Matplotlib Users

Subject: Re: [Matplotlib-users] FW: traceback when import matplotlib.pyplot twice



See https://github.com/matplotlib/matplotlib/pull/3638



That might help to make sure that things tear them selves down in the right order.



Tom



On Sat, Oct 11, 2014 at 10:12 AM, Phil Elson <pel...@gm...> wrote:

>

> On 10 October 2014 19:10, Thomas Caswell <tca...@gm...> wrote:

>>

>> I suspect a better fix is to change all of the staticmethods ->

>> classmethods

>

>

>

> +1







--

Thomas Caswell

tca...@gm...