end?
>
> Christoph
>
>
>
> On 8/11/2010 2:31 PM, stetrick wrote:
>>
>> I removed and reinstalled everything, and I'm still getting it.
>>
>> I am using the multiprocessing lib. Each process then produces a graph
>> with
>> matplotlib, w
Adding a close() at the end didn't do anything - still get the same message.
stetrick wrote:
>
> I removed and reinstalled everything, and I'm still getting it.
>
> I am using the multiprocessing lib. Each process then produces a graph
> with matplotlib, which
I removed and reinstalled everything, and I'm still getting it.
I am using the multiprocessing lib. Each process then produces a graph with
matplotlib, which is only done with Savefig (never interactively displaced
during the creation process). I have nothing special in the configuration
- jus
Should probably indicate that it is the MKV versions
stetrick wrote:
>
>
>
> Christoph Gohlke wrote:
>>
>>
>>
>> On 8/9/2010 3:09 PM, stetrick wrote:
>>>
>>> I am now getting a message that says:
>>>
>>> Fatal Pyth
Christoph Gohlke wrote:
>
>
>
> On 8/9/2010 3:09 PM, stetrick wrote:
>>
>> I am now getting a message that says:
>>
>> Fatal Python error: PyEval_RestoreThread: NULL tstate
>>
>> This application has requested the Runtime to terminate it in
I am now getting a message that says:
Fatal Python error: PyEval_RestoreThread: NULL tstate
This application has requested the Runtime to terminate it in an unusual
way.
This is with matplotlib 1.0.0, but all versions are 64-bit (python, numpy,
matplotlib).
Is this something I can fix or ignor
