matplotlib-users Mailing List for matplotlib

Works fine for
{{{
 : python 
Python 2.7.10 (default, Sep 15 2015, 11:26:42) 
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
/Users/smithsp/.pyhistory
>>> import matplotlib
>>> matplotlib.__version__
'1.4.3'
>>> import numpy
>>> numpy.__version__
'1.9.2'
>>> matplotlib.get_backend()
u’MacOSX'
}}}
All are obtained through MacPorts on OSX 10.9.5.
-Sterling
On Sep 16, 2015, at 6:50AM, Benjamin Root <ben...@gm...> wrote:
> Btw, I can't reproduce the problem using matplotlib master, numpy master and linux. I know it isn't at all similar to your setup, but it is a data point.
> 
> On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...> wrote:
> What version of numpy do you have installed?
> 
> On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...> wrote:
> OS: Windows 8.1 Pro
> 
> matplotlib version: 1.4.3
> 
> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
> 
> customizations: none
> 
> Sample Program: attached py file; this is a Physics homework problem; I have the answers I need, but would like to fix the errors to be able to label all lines.
> 
> Debug output in attached output.txt file
> 
> If you uncomment line 180, the error is reported as if it came from that line even though there is no float64 on that line (savefig). If commented, it does not report a line from my .py file...
> 
> If you make line 170 read as follows, the error goes away:
> 
> if (maxTerm<32):
> 
> This suggests to me that the additional labels for the 32, 64, 128, and 154 term runs is what is triggering the bug, but I cannot figure out what it is. 
> 
> Also, separate note, just about any time I make figures, when closing the last figure I get a python.exe app crash and this message:
> 
> alloc: invalid block: 00000000044E7680: 0 d
> 
> 
> Thank you for any help,
> Bobby
> 
> 
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
> 
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Btw, I can't reproduce the problem using matplotlib master, numpy master
and linux. I know it isn't at all similar to your setup, but it is a data
point.
On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...> wrote:
> What version of numpy do you have installed?
>
> On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
> wrote:
>
>> OS: Windows 8.1 Pro
>>
>> matplotlib version: 1.4.3
>>
>> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
>>
>> customizations: none
>>
>> Sample Program: attached py file; this is a Physics homework problem; I
>> have the answers I need, but would like to fix the errors to be able to
>> label all lines.
>>
>> Debug output in attached output.txt file
>>
>> If you uncomment line 180, the error is reported as if it came from that
>> line even though there is no float64 on that line (savefig). If commented,
>> it does not report a line from my .py file...
>>
>> If you make line 170 read as follows, the error goes away:
>>
>> if (maxTerm<32):
>>
>> This suggests to me that the additional labels for the 32, 64, 128, and
>> 154 term runs is what is triggering the bug, but I cannot figure out what
>> it is.
>>
>> Also, separate note, just about any time I make figures, when closing the
>> last figure I get a python.exe app crash and this message:
>>
>> alloc: invalid block: 00000000044E7680: 0 d
>>
>>
>> Thank you for any help,
>> Bobby
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> Get real-time metrics from all of your servers, apps and tools
>> in one place.
>> SourceForge users - Click here to start your Free Trial of Datadog now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>

What version of numpy do you have installed?
On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
wrote:
> OS: Windows 8.1 Pro
>
> matplotlib version: 1.4.3
>
> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
>
> customizations: none
>
> Sample Program: attached py file; this is a Physics homework problem; I
> have the answers I need, but would like to fix the errors to be able to
> label all lines.
>
> Debug output in attached output.txt file
>
> If you uncomment line 180, the error is reported as if it came from that
> line even though there is no float64 on that line (savefig). If commented,
> it does not report a line from my .py file...
>
> If you make line 170 read as follows, the error goes away:
>
> if (maxTerm<32):
>
> This suggests to me that the additional labels for the 32, 64, 128, and
> 154 term runs is what is triggering the bug, but I cannot figure out what
> it is.
>
> Also, separate note, just about any time I make figures, when closing the
> last figure I get a python.exe app crash and this message:
>
> alloc: invalid block: 00000000044E7680: 0 d
>
>
> Thank you for any help,
> Bobby
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

OS: Windows 8.1 Pro
matplotlib version: 1.4.3
where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
customizations: none
Sample Program: attached py file; this is a Physics homework problem; I
have the answers I need, but would like to fix the errors to be able to
label all lines.
Debug output in attached output.txt file
If you uncomment line 180, the error is reported as if it came from that
line even though there is no float64 on that line (savefig). If commented,
it does not report a line from my .py file...
If you make line 170 read as follows, the error goes away:
if (maxTerm<32):
This suggests to me that the additional labels for the 32, 64, 128, and 154
term runs is what is triggering the bug, but I cannot figure out what it
is.
Also, separate note, just about any time I make figures, when closing the
last figure I get a python.exe app crash and this message:
alloc: invalid block: 00000000044E7680: 0 d
Thank you for any help,
Bobby