matplotlib-devel Mailing List for matplotlib

On 18-Sep-09, at 6:42 PM, David Warde-Farley wrote:
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line
> 627, in __init__
>     user_ns,user_global_ns,b2 =
> self._matplotlib_config(name,user_ns,user_global_ns)
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line
> 556, in _matplotlib_config
>     import matplotlib.pylab as pylab
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/matplotlib/pylab.py", line 206, in <module>
>     from matplotlib import mpl  # pulls in most modules
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/matplotlib/mpl.py", line 1, in <module>
>     from matplotlib import artist
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/matplotlib/artist.py", line 5, in <module>
>     from transforms import Bbox, IdentityTransform, TransformedBbox,
> TransformedPath
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
> python2.6/site-packages/matplotlib/transforms.py", line 34, in  
> <module>
>     from matplotlib._path import affine_transform
> ImportError: numpy.core.multiarray failed to import

Looking a little harder at this (after downloading the source) I'm  
positively at a loss, since multiarray doesn't seem to be explicitly  
imported anywhere in matplotlib. Furthermore, importing  
numpy.core.multiarray from ipython works just fine.

Moreover, I just built matplotlib-0.99.1rc1 from source and the  
problem doesn't manifest. _Weird_. Any idea what's going on?

David

On 18-Sep-09, at 6:09 PM, John Hunter wrote:

> Could you try the 99.1rc release candidate linked to in the "news"  
> box on the mpl homepage?  I did fix some link problems in the osx  
> binaries since 0.99.0.

Just tried, unfortunately it doesn't seem to like my setup either:

RuntimeError: FATAL: module compiled aslittle endian, but detected  
different endianness at runtime
Traceback (most recent call last):
   File "/Library/Frameworks/Python.framework/Versions/2.6/bin/ 
ipython", line 8, in <module>
     load_entry_point('ipython==0.10', 'console_scripts', 'ipython')()
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/ipapi.py", line  
556, in launch_new_instance
     ses = make_session(user_ns,shellclass)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/ipapi.py", line  
684, in make_session
     return IPython.Shell.start(user_ns)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line  
1241, in start
     return shell(user_ns = user_ns)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line  
1106, in __init__
     shell_class=MatplotlibShell)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line  
73, in __init__
     debug=debug,shell_class=shell_class)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/ipmaker.py",  
line 100, in make_IPython
     embedded=embedded,**kw)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line  
627, in __init__
     user_ns,user_global_ns,b2 =  
self._matplotlib_config(name,user_ns,user_global_ns)
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/ipython-0.10-py2.6.egg/IPython/Shell.py", line  
556, in _matplotlib_config
     import matplotlib.pylab as pylab
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/matplotlib/pylab.py", line 206, in <module>
     from matplotlib import mpl  # pulls in most modules
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/matplotlib/mpl.py", line 1, in <module>
     from matplotlib import artist
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/matplotlib/artist.py", line 5, in <module>
     from transforms import Bbox, IdentityTransform, TransformedBbox,  
TransformedPath
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/matplotlib/transforms.py", line 34, in <module>
     from matplotlib._path import affine_transform
ImportError: numpy.core.multiarray failed to import

Could you try the 99.1rc release candidate linked to in the "news" box  
on the mpl homepage?  I did fix some link problems in the osx binaries  
since 0.99.0.



On Sep 18, 2009, at 4:53 PM, David Warde-Farley <dw...@cs...>  
wrote:

> Using the binaries at matplotlib.sf.net:
>
>
> dwf@strafe:~$ ipython -pylab
> Python 2.6.2 (r262:71600, Apr 16 2009, 09:17:39)
> Type "copyright", "credits" or "license" for more information.
>
> IPython 0.10 -- An enhanced Interactive Python.
> ?         -> Introduction and overview of IPython's features.
> %quickref -> Quick reference.
> help      -> Python's own help system.
> object?   -> Details about 'object'. ?object also works, ?? prints  
> more.
>
>   Welcome to pylab, a matplotlib-based Python environment.
>   For more information, type 'help(pylab)'.
>
> In [1]: matplotlib.__version__Out[1]: '0.99.0'
>
> In [2]: matplotlib.get_backend()
> Out[2]: 'TkAgg'
>
> In [3]: plt.figure()
> Bus error
>
>
> GDB says this was the problem:
>
>>>> fig = plt.figure()
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000028
> 0x00e04d95 in PyArray_INCREF ()
>
> I wonder if this is caused by me having my own freetype installed
> under /usr/local (I was installing Chaco the other day from source,
> and thus required it), and the dynamic linker getting confused about
> which version to use?
>
> David
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register  
> now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Using the binaries at matplotlib.sf.net:


dwf@strafe:~$ ipython -pylab
Python 2.6.2 (r262:71600, Apr 16 2009, 09:17:39)
Type "copyright", "credits" or "license" for more information.

IPython 0.10 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object'. ?object also works, ?? prints more.

   Welcome to pylab, a matplotlib-based Python environment.
   For more information, type 'help(pylab)'.

In [1]: matplotlib.__version__Out[1]: '0.99.0'

In [2]: matplotlib.get_backend()
Out[2]: 'TkAgg'

In [3]: plt.figure()
Bus error


GDB says this was the problem:

 >>> fig = plt.figure()

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000028
0x00e04d95 in PyArray_INCREF ()

I wonder if this is caused by me having my own freetype installed  
under /usr/local (I was installing Chaco the other day from source,  
and thus required it), and the dynamic linker getting confused about  
which version to use?

David

On Fri, Sep 18, 2009 at 17:44, Michael Droettboom <md...@st...> wrote:
> Thanks.  The subslicing optimization added in 0.99 was truncating the polar
> path.  Subslicing has been made more "cautious" now and will only be applied
> when the axes are rectilinear and non-logarithmic.
>
> Interestingly, there was already a test in the test framework for this bug,
> but the baseline image was wrong :)

Thanks for fixing this :)

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On Fri, Sep 18, 2009 at 17:16, John Hunter <jd...@gm...> wrote:
> I filed a report at
> https://sourceforge.net/tracker/?func=browse&group_id=80706&atid=560720.

Ok, next time I'll file a bug on SF issue tracker instead of writing here.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Michael Droettboom wrote:
> Thanks.  The subslicing optimization added in 0.99 was truncating the 
> polar path.  Subslicing has been made more "cautious" now and will only 
> be applied when the axes are rectilinear and non-logarithmic.
>
> Interestingly, there was already a test in the test framework for this 
> bug, but the baseline image was wrong :)
I see you fixed that, too -- thanks. I can't remember the history of
this one particular test -- I think maybe I inherited it without a test
image or perhaps I just over-enthusiastically copied a broken image
without realizing it as such.

These unit tests have already shown their worth I think (fixing
non-deterministic layout, getting a grip on freetype, etc.), and their
value in preventing mistakes and regressions from creeping in is hard to
perceive but I think is also very real. As more and more tests are added
(and broken baseline images and test cases are fixed), the number of
regressions will almost certainly drop.

-Andrew

Thanks.  The subslicing optimization added in 0.99 was truncating the 
polar path.  Subslicing has been made more "cautious" now and will only 
be applied when the axes are rectilinear and non-logarithmic.

Interestingly, there was already a test in the test framework for this 
bug, but the baseline image was wrong :)

Mike

Sandro Tosi wrote:
> Hi all,
> with the simple code here below
>
> $ ipython -pylab
>
> In [1]: import numpy as np
>
> In [2]: theta = np.arange(0., 2., 1./180.)*np.pi
>
> In [3]: plt.polar(3*theta, theta/5)
>
> I obtain the attached images with 0.98.5.3 and 0.99.{0.1rc1} (didn't
> have time to test against SVN).
>
> AFAIUI, the 0.98.5.3 should be the correct behavior, so in 0.99.x
> there's a regression.
>
> Regards,
>   
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Fri, Sep 18, 2009 at 9:48 AM, Sandro Tosi <mat...@gm...> wrote:
> Hi all,
> with the simple code here below
>
> $ ipython -pylab
>
> In [1]: import numpy as np
>
> In [2]: theta = np.arange(0., 2., 1./180.)*np.pi
>
> In [3]: plt.polar(3*theta, theta/5)
>
> I obtain the attached images with 0.98.5.3 and 0.99.{0.1rc1} (didn't
> have time to test against SVN).
>
> AFAIUI, the 0.98.5.3 should be the correct behavior, so in 0.99.x
> there's a regression.

I filed a report at
https://sourceforge.net/tracker/?func=browse&group_id=80706&atid=560720.

JDH

Hi all,
with the simple code here below

$ ipython -pylab

In [1]: import numpy as np

In [2]: theta = np.arange(0., 2., 1./180.)*np.pi

In [3]: plt.polar(3*theta, theta/5)

I obtain the attached images with 0.98.5.3 and 0.99.{0.1rc1} (didn't
have time to test against SVN).

AFAIUI, the 0.98.5.3 should be the correct behavior, so in 0.99.x
there's a regression.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Apparently usetex_demo.py and dannys_example.py are same
(matplotlib/examples).

The latter might be deleted if no reference exist for that file.

-- 
Gökhan

Jouni K. Seppänen wrote:
> I just happened to type getp(gca()) on matplotlib 0.99.0, and the output
> looks all garbled:

Fixed in r7780 (branch) and 7781 (trunk).

Eric

> 
>>>> getp(gca())
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/axes.py:1269: DeprecationWarning: use ax.patch instead
>   warnings.warn('use ax.patch instead', DeprecationWarning)
>     stable = box
>     a = 1.0
>     or = C
>     ated = False
>     ct = auto
>     scale_on = True
>     scalex_on = True
>     scaley_on = True
>      = Axes(0.125,0.1;0.775x0.8)
>     _locator = None
>     _bgcolor = w
> [...]
> 
> It's been a long time since I last tried this, but does anyone have an
> idea what changes could have caused this? Could it be related to the
> ReST formatting in the docstrings?
> 
> Querying single attributes as in getp(gca(), 'yscale') seems to work
> fine, it's just this listing of all attributes that seems to be broken.
>