Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-07 Thread Derek Homeier
On 06.07.2012, at 3:49PM, Damon McDougall wrote: >> >> When I tested on Mac OS X 10.6 I found that most unit tests were somehow >> missing. Rather than try to diagnose the problem, I built a new binary >> on 10.6, confirmed that it installed properly (with all unit tests) on >> 10.6 and 10.7,

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-06 Thread Russell E. Owen
In article , Jouni K. Seppänen wrote: > Russell Owen writes: > > > By the way: I installed ghostscript from source and Inkscape > > application from binary. More tests pass, but many still show K. My > > guess is that matplotlib can see ghostscript but not the Inkscape > > application (no surp

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-06 Thread Damon McDougall
On Thu, Jul 05, 2012 at 07:43:39PM +, Russell E. Owen wrote: > In article , > Russell Owen wrote: > > > I just uploaded the Mac binaries. > > > > Several minor concerns: > > - Many unit tests failed on Mac OS X 10.4 (which is where I build the > > 10.3.9 > > version) due to "too many file

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Jouni K . Seppänen
Russell Owen writes: > By the way: I installed ghostscript from source and Inkscape > application from binary. More tests pass, but many still show K. My > guess is that matplotlib can see ghostscript but not the Inkscape > application (no surprise). Inkscape has too many dependencies for me > to

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Eric Firing
On 07/05/2012 01:41 PM, Russell Owen wrote: > By the way: I installed ghostscript from source and Inkscape application > from binary. More tests pass, but many still show K. My guess is that > matplotlib can see ghostscript but not the Inkscape application (no > surprise). Inkscape has too many dep

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Russell Owen
By the way: I installed ghostscript from source and Inkscape application from binary. More tests pass, but many still show K. My guess is that matplotlib can see ghostscript but not the Inkscape application (no surprise). Inkscape has too many dependencies for me to want to try to build it from

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Russell Owen
When I say "somehow missing" I'm not referring to the K (known fail). I'm referring to exceptions and tracebacks caused by trying to import test_X for various value of X: the modules were actually missing. I've never seen that before, so I was quite shocked. Normally I build on the oldest versio

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread John Hunter
On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen wrote: > > When I tested on Mac OS X 10.6 I found that most unit tests were somehow > missing. Rather than try to diagnose the problem, I built a new binary > on 10.6, confirmed that it installed properly (with all unit tests) on > 10.6 and 10.7, th

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Russell E. Owen
In article , Russell Owen wrote: > I just uploaded the Mac binaries. > > Several minor concerns: > - Many unit tests failed on Mac OS X 10.4 (which is where I build the 10.3.9 > version) due to "too many files open", but the same binary looks fine on > 10.5. > - The 64-bit version (10.6 and l

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-05 Thread Russell Owen
I just uploaded the Mac binaries. Several minor concerns: - Many unit tests failed on Mac OS X 10.4 (which is where I build the 10.3.9 version) due to "too many files open", but the same binary looks fine on 10.5. - The 64-bit version (10.6 and later) had one unexpected failure on 10.7 (I have n

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-03 Thread Christoph Gohlke
On 6/30/2012 1:24 PM, Christoph Gohlke wrote: > On 6/30/2012 12:55 PM, John Hunter wrote: >> >> >> On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez > > wrote: >> >> On Sat, Jun 30, 2012 at 11:46 AM, John Hunter > > wrote: >> > Wel

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-07-01 Thread Sandro Tosi
On Sun, Jul 1, 2012 at 2:25 AM, John Hunter wrote: > It certainly was outside you control Sandro. You gave us ample warning and > reminders. I misinterpreted the June 30th freeze date to mean we needed to > get it in by that date, but maybe it meant before, or maybe at some earlier > time today.

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
On Jun 30, 2012, at 6:27 PM, Derek Homeier wrote: >> >> And none of the rules match this situation. RC2 will be :) > > What about the very last one? > > "For packages which missed the freeze only for reasons outside of the control > of the maintainers, we might be generous, but you need to c

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Derek Homeier
On 01.07.2012, at 12:17AM, Sandro Tosi wrote: >> >> Just out of curiosity, what is the mismatch? (I believe you, I just >> know very little about the debian process). > > These are the rules: http://release.debian.org/wheezy/freeze_policy.html > > And none of the rules match this situation. RC

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Sandro Tosi
On Sun, Jul 1, 2012 at 12:08 AM, Fernando Perez wrote: > On Sat, Jun 30, 2012 at 3:07 PM, Sandro Tosi wrote: >> It's probably a nomenclature difference: it's a "freeze exception" so >> asking to overrule the freeze in place and allow a package to enter >> testing, but it must match basic rules, b

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Fernando Perez
On Sat, Jun 30, 2012 at 3:07 PM, Sandro Tosi wrote: > It's probably a nomenclature difference: it's a "freeze exception" so > asking to overrule the freeze in place and allow a package to enter > testing, but it must match basic rules, but in this case they are not > matched. Just out of curiosit

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Sandro Tosi
On Sun, Jul 1, 2012 at 12:04 AM, John Hunter wrote: > But I thought this is exactly when an *exception* is needed: when one > doesn't match the rules. It's probably a nomenclature difference: it's a "freeze exception" so asking to overrule the freeze in place and allow a package to enter testing,

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
On Jun 30, 2012, at 4:35 PM, Sandro Tosi wrote > > I've just reviewed the rules, and sadly realized the final mpl release > doesn't match them, so it's not worth asking for the exception. >> But I thought this is exactly when an *exception* is needed: when one doesn't match the rules. ---

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Sandro Tosi
Hello, On Sat, Jun 30, 2012 at 10:54 PM, John Hunter wrote: > Yeah, the diff Sandro is referring to for us is just between rc2 and final.   > Hopefully he can argue that since r1.1.1-rc2 is already in, they can accept > this minor diff to final. I've just reviewed the rules, and sadly realized

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Fernando Perez
On Sat, Jun 30, 2012 at 1:54 PM, John Hunter wrote: > Yeah, the diff Sandro is referring to for us is just between rc2 and final.   > Hopefully he can argue that since r1.1.1-rc2 is already in, they can accept > this minor diff to final. In our case unfortunately we didn't have time to cut an RC

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
On Jun 30, 2012, at 3:46 PM, Fernando Perez > Wow, I guess it paid off for us to stay up until 2am last night to get > IPython in... Our diff was enormous so we would have not been allowed > in at al. Whew :) Yeah, the diff Sandro is referring to for us is just between rc2 and final. Hope

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
On Jun 30, 2012, at 3:42 PM, Sandro Tosi wrote: > Hello John, > thanks for your effort! but... > > > ... we're already too late for the Debian freeze :( the diff is quite > small, so I'll ask for a freeze exception. Ouch. Sorry for the screwup. Good luck with the exception request: all tha

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Fernando Perez
On Sat, Jun 30, 2012 at 1:42 PM, Sandro Tosi wrote: > ... we're already too late for the Debian freeze :( the diff is quite > small, so I'll ask for a freeze exception. Wow, I guess it paid off for us to stay up until 2am last night to get IPython in... Our diff was enormous so we would have not

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Sandro Tosi
Hello John, thanks for your effort! but... On Sat, Jun 30, 2012 at 9:55 PM, John Hunter wrote: > OK, the v1.1.1 tarball is up > at https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1 > and this is now the download folder the main site points to.  I'm leaving up > the rc2

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Christoph Gohlke
On 6/30/2012 12:55 PM, John Hunter wrote: > > > On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez > wrote: > > On Sat, Jun 30, 2012 at 11:46 AM, John Hunter > wrote: > > Well, looks like we better get moving then ;-) > > Go MPL!

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Fernando Perez
On Sat, Jun 30, 2012 at 12:55 PM, John Hunter wrote: > OK, the v1.1.1 tarball is up > at https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1 > and this is now the download folder the main site points to.  I'm leaving up > the rc2 binaries til Russell and Christoph can bui

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez wrote: > On Sat, Jun 30, 2012 at 11:46 AM, John Hunter wrote: > > Well, looks like we better get moving then ;-) > > Go MPL! It would be great to have matching releases of IPython and > MPL, just in time for the Debian freeze and SciPy 2012 :) > >

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread Fernando Perez
On Sat, Jun 30, 2012 at 11:46 AM, John Hunter wrote: > Well, looks like we better get moving then ;-) Go MPL! It would be great to have matching releases of IPython and MPL, just in time for the Debian freeze and SciPy 2012 :) Cheers, f

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-30 Thread John Hunter
Well, looks like we better get moving then ;-). I have some time today to do this (sorry for dropping out last week). The only PR I see that perhaps should go in is https://github.com/matplotlib/matplotlib/pull/961 Anything I'm missing? I'm going to start testing this for the final release and

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-21 Thread Sandro Tosi
Hi all, On Sat, Jun 9, 2012 at 11:14 PM, John Hunter wrote: > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site Is there a timeline for the final release? The Debian freeze is announced for June 30th. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matr

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-13 Thread Michael Droettboom
I don't think this has anything to do with matplotlib, but instead just with pygobject (or perhaps just gtk itself) on Fedora 17. I suspect that this fedora bug is responsible: https://bugzilla.redhat.com/show_bug.cgi?id=790053 Importing gtk is enough to produce this warning: In [1]: import g

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-13 Thread Neal Becker
Since installing this on fedora f17 x86_64, I see this warning: ipython -pylab ... ** (process:26729): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (process:26729): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-13 Thread John Hunter
On Wed, Jun 13, 2012 at 1:03 PM, Michael Droettboom wrote: > Is there a slight mix-up in the commits?  In the email John sent out, it had > commit f763cd11f50437568f8146b822ca8f25647cbb61 at the top of the log > (alternative baseline image for mathfont_stix_14.png). The tag is correct, the email

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-13 Thread Michael Droettboom
On 06/13/2012 01:29 PM, Benjamin Root wrote: On Mon, Jun 11, 2012 at 2:23 PM, Michael Droettboom > wrote: On 06/11/2012 02:17 PM, John Hunter wrote: > On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboommailto:md...@stsci.edu>> wrote: >> John: Do you k

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-13 Thread Benjamin Root
On Mon, Jun 11, 2012 at 2:23 PM, Michael Droettboom wrote: > On 06/11/2012 02:17 PM, John Hunter wrote: > > On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboom > wrote: > >> John: Do you know which git revision you made the tarballs from? I'll > go > >> ahead and tag it. > > > https://github.c

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Michael Droettboom
On 06/11/2012 02:17 PM, John Hunter wrote: > On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboom wrote: >> John: Do you know which git revision you made the tarballs from? I'll go >> ahead and tag it. > https://github.com/matplotlib/matplotlib/commit/97f713098a71c70d70c46602794c2a0fd126b614 Than

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread John Hunter
On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboom wrote: > John: Do you know which git revision you made the tarballs from?  I'll go > ahead and tag it. https://github.com/matplotlib/matplotlib/commit/97f713098a71c70d70c46602794c2a0fd126b614 ---

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Sandro Tosi
On Mon, Jun 11, 2012 at 3:40 PM, RuiDC wrote: > > Testing looks good only two known fails for me against the rc2 binaries that > I spotted on SF on both Windows7 amd64 and Windows XP x86_32 (both Python > 2.7.3). > > The only thing out of the ordinary for me is the following on both: > > matplotli

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Michael Droettboom
John: Do you know which git revision you made the tarballs from? I'll go ahead and tag it. Mike On 06/09/2012 09:52 PM, Benjamin Root wrote: Don't forget to tag the rc in git! On Sat, Jun 9, 2012 at 6:40 PM, John Hunter > wrote: On Sat, Jun 9, 2012 at 5:33 PM,

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread RuiDC
Testing looks good only two known fails for me against the rc2 binaries that I spotted on SF on both Windows7 amd64 and Windows XP x86_32 (both Python 2.7.3). The only thing out of the ordinary for me is the following on both: matplotlib.tests.test_axes.test_markevery_line.test ... ok C:\Python2

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Sandro Tosi
On Sat, Jun 9, 2012 at 11:14 PM, John Hunter wrote: > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ Debian package built and uploaded - thanks! Cheers, -- Sandro Tosi (aka morph, morpheus, matrix

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Benjamin Root
Don't forget to tag the rc in git! On Sat, Jun 9, 2012 at 6:40 PM, John Hunter wrote: > On Sat, Jun 9, 2012 at 5:33 PM, John Hunter wrote: > > On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing wrote: > >> It also has backend_gdk.c (supposed to be a temporary copy of > >> _backend_gdk.c) and some oth

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread John Hunter
Thanks -- I've already started the process for the files, but can you test upload something into the 1.1 folder (easy to subsequently delete). I just made you a project admin. I'd like to get this figure out eventually! On Sat, Jun 9, 2012 at 8:53 PM, Christoph Gohlke wrote: > Hi John, > > the

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-11 Thread Christoph Gohlke
Hi John, the matplotlib-1.1.1rc2.win installers are at . I am again unable to upload them to SF. They are built against numpy 1.6.2 and include the test files. All tests pass on Python 2.7, 32 and 64 bit. Christoph On 6/9/2012 2:14 PM,

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-09 Thread John Hunter
On Sat, Jun 9, 2012 at 5:33 PM, John Hunter wrote: > On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing wrote: >> It also has backend_gdk.c (supposed to be a temporary copy of >> _backend_gdk.c) and some others like it. > > OK, I'll rebuild them super clean...  I know what went wrong. Just uploaded tw

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-09 Thread John Hunter
On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing wrote: > It also has backend_gdk.c (supposed to be a temporary copy of > _backend_gdk.c) and some others like it. OK, I'll rebuild them super clean... I know what went wrong.

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-09 Thread Eric Firing
On 06/09/2012 12:21 PM, John Hunter wrote: > On Sat, Jun 9, 2012 at 5:11 PM, Eric Firing wrote: >> On 06/09/2012 11:14 AM, John Hunter wrote: >>> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site >> >> John, >> >> Is it intentional that the tarballs include doc/build? > > It isn't int

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-09 Thread John Hunter
On Sat, Jun 9, 2012 at 5:11 PM, Eric Firing wrote: > On 06/09/2012 11:14 AM, John Hunter wrote: >> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > John, > > Is it intentional that the tarballs include doc/build? It isn't intentional and it looks like it only affected the "notes

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

2012-06-09 Thread Eric Firing
On 06/09/2012 11:14 AM, John Hunter wrote: > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site John, Is it intentional that the tarballs include doc/build? Eric > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ > > As soon as we get binaries, I'll s