Re: [matplotlib-devel] I added a wheels build to binary build framework

2014-03-24 Thread Benjamin Root
I thought we fixed this one...

Seems like we haven't as there is an open issue for it:
https://github.com/matplotlib/matplotlib/issues/2842


On Sun, Mar 23, 2014 at 7:07 AM, Matthew Brett wrote:

> Hi,
>
> On Sun, Mar 23, 2014 at 1:46 AM, Matthew Brett 
> wrote:
> > Hi,
> >
> > On Sat, Dec 14, 2013 at 12:28 PM, Matthew Brett 
> wrote:
> >> Hi,
> >>
> >> Prompted by Chris B, I just added matplotlib wheels building to the
> >> framework here:
> >>
> >> https://github.com/matthew-brett/mpl-osx-binaries
> >>
> >> Instructions for build in the README.
> >>
> >> Sorry - am In Cuba at the moment with very low internet bandwidth and
> >> can't upload the wheels, but they should be simple to build (or I
> >> messed up with the instructions),
> >
> > Following up on this one - I have built OSX wheels for python 2.7, 3.3
> > and 3.4 here:
> >
> > https://nipy.bic.berkeley.edu/scipy_installers/
> >
> > You should now be able to do:
> >
> > # upgrade to latest pip
> > pip install --upgrade pip
> > # get fully binary install of matplotlib
> > pip install --find-links=https://nipy.bic.berkeley.edu/scipy_installers
> > matplotlib
> >
> > I've tested on a bare 10.6 machine for Python 2.7, will test for 3.3
> > and 3.4 - but - could y'all give the installation a try and see if it
> > works for you?  It will work as well into a virtualenv.  There are
> > also numpy wheels there so you can get the full stack with that
> > command.
>
> Yes, they seem to work on bare 10.6 on all three python versions.  I
> got one failure on python 3.4 but it didn't look related to the wheel:
>
> ==
> FAIL: matplotlib.tests.test_basic.test_override_builtins
> --
> Traceback (most recent call last):
>   File
> "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/nose/case.py",
> line 198, in runTest
> self.test(*self.arg)
>   File
> "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/matplotlib/tests/test_basic.py",
> line 38, in test_override_builtins
> assert not overridden
> nose.proxy.AssertionError:
>  >> begin captured stdout << -
> '__spec__' was overridden in globals().
>
> - >> end captured stdout << --
>
> Cheers,
>
> Matthew
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] PR reviews for 1.4

2014-03-24 Thread Thomas Caswell
Hello all,

I currently have 14 open PR's (most of which have an associated
issue).  If these could get reviewed/merged it would go along way to
cutting down the number of outstanding issues we have to get through
before we can cut 1.4.0

https://github.com/matplotlib/matplotlib/issues/created_by/tacaswell?direction=desc&labels=needs_review&milestone=10&page=1&sort=created&state=open

https://github.com/matplotlib/matplotlib/issues/created_by/tacaswell?direction=desc&labels=needs_review&milestone=9&page=1&sort=created&state=open

https://github.com/matplotlib/matplotlib/issues/created_by/tacaswell?direction=desc&labels=needs_review&milestone=7&page=1&sort=created&state=open

Tom
-- 
Thomas Caswell
[email protected]

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Axes properties are cleared after offsetting spines

2014-03-24 Thread Stan West

On 2014-03-24 14:08, Stan West wrote:
May I suggest that you look at the mailing list thread from that time 
[1], try the patch in the thread, and see whether your issue is 
resolved? This solution doesn't provide a work-around in your code, 
but it may fix the problem at the root.
Paul, I just found the work-around that I used in my code. Define the 
following function:


   def set_spine_position(spine, position):
"""
Set the spine's position without resetting an associated axis.

As of matplotlib v. 1.0.0, if a spine has an associated axis, then

spine.set_position() calls axis.cla(), which resets locators, 
formatters,
etc.  We temporarily replace that call with axis.reset_ticks(), which is
sufficient for our purposes.
"""
axis = spine.axis
if axis is not None:
cla = axis.cla
axis.cla = axis.reset_ticks
spine.set_position(position)
if axis is not None:
axis.cla = cla

(The mention of v. 1.0.0 in the docstring is just the version I was 
using at the time, not necessarily the earliest version with this 
issue.) Then replace method calls like "spine.set_position(pos)" with 
the function call "set_spine_position(spine, pos)". I hope this helps.
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Axes properties are cleared after offsetting spines

2014-03-24 Thread Stan West

On 2014-02-05 02:26, Paul Hobson wrote:
I noticed that when you offset the spines of an Axes object, the 
labels, ticks, and ticklabels/formatting get mostly cleared. Is this 
intentional and is there a way to prevent (or undo) it?

[...]

Paul, I may have encountered the same issue a few years ago. May I 
suggest that you look at the mailing list thread from that time [1], try 
the patch in the thread, and see whether your issue is resolved? This 
solution doesn't provide a work-around in your code, but it may fix the 
problem at the root. I took a brief look at the current state of 
spines.py, and I found only the same instances of "self.axis.cla()" that 
the patch changes to "self.axis.reset_ticks()".


Kind regards,

Stan

[1] 
http://matplotlib.1069221.n5.nabble.com/Spine-set-position-unexpectedly-clears-axis-td37865.html, 
29 Sep. 2010.
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel