Ryanitus wrote:
> I may have found a bug in the __setitem__ method of the maxdict class.
>
Fixed--thanks for pointing it out.
Eric
> Since a dictionary is a mapping class, if an item is set that already
> exists, it overwrites the previous. However, you are still appending that
> item to _kill
On Fri, Sep 18, 2009 at 7:01 PM, Andrew Straw wrote:
> Maybe the MPL binary was built with a numpy svn version that had API
> incompatibilities with numpy releases?
I built the python2.6 OSX 0.99.1rc1 binary with the numpy from the
1.3.0 dmg installer from the sf site, intentionally not using my
David Warde-Farley wrote:
> 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
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)
>
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: FATA
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
wrote:
> Using the binaries at matplotlib.sf.net:
>
>
> d...@strafe:~$ ipython -pyla
Using the binaries at matplotlib.sf.net:
d...@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.
%qu
On Fri, Sep 18, 2009 at 17:44, 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 al
On Fri, Sep 18, 2009 at 17:16, John Hunter 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
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 frame
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 baselin
On Fri, Sep 18, 2009 at 9:48 AM, 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.{
12 matches
Mail list logo
