From: Christoph G. <cg...@uc...> - 2012-06-30 20:24:22
|
On 6/30/2012 12:55 PM, John Hunter wrote: > > > On Sat, Jun 30, 2012 at 2:40 PM, Fernando Perez <fpe...@gm... > <mailto:fpe...@gm...>> wrote: > > On Sat, Jun 30, 2012 at 11:46 AM, John Hunter <jd...@gm... > <mailto:jd...@gm...>> 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 :) > > > 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 build v1.1.1 > binaries and we get them uploaded. Sandro, if you're around, you are > good to go for including this in debian, hopefully squeaking in under > the freeze (sorry for the last minute push). > > I will hold off on the users and announce list emails til the updated > binaries are up. > > Tagged: git tag v1.1.1 7e47149a7b05f8e5cf1cc899a7e4e7c90dd4244f > > Thanks to all! > JDH Here are the Windows installers, built against numpy 1.6.2. Sorry, I can not upload them to SF. There seems to be some permission problems that the SF admins would need to fix manually. <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib> Christoph |
From: Christoph G. <cg...@uc...> - 2012-07-03 16:49:16
|
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 <fpe...@gm... >> <mailto:fpe...@gm...>> wrote: >> >> On Sat, Jun 30, 2012 at 11:46 AM, John Hunter <jd...@gm... >> <mailto:jd...@gm...>> 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 :) >> >> >> 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 build v1.1.1 >> binaries and we get them uploaded. Sandro, if you're around, you are >> good to go for including this in debian, hopefully squeaking in under >> the freeze (sorry for the last minute push). >> >> I will hold off on the users and announce list emails til the updated >> binaries are up. >> >> Tagged: git tag v1.1.1 7e47149a7b05f8e5cf1cc899a7e4e7c90dd4244f >> >> Thanks to all! >> JDH > > Here are the Windows installers, built against numpy 1.6.2. Sorry, I can > not upload them to SF. There seems to be some permission problems that > the SF admins would need to fix manually. > > <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib> > > Christoph > Sourceforge has fixed the permissions. I uploaded the Windows installers. Christoph |
From: Sandro T. <mo...@de...> - 2012-06-30 20:42:41
|
Hello John, thanks for your effort! but... On Sat, Jun 30, 2012 at 9:55 PM, John Hunter <jd...@gm...> 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 build v1.1.1 binaries and we > get them uploaded. Sandro, if you're around, you are good to go for > including this in debian, hopefully squeaking in under the freeze (sorry for > the last minute push). ... we're already too late for the Debian freeze :( the diff is quite small, so I'll ask for a freeze exception. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
From: John H. <jd...@gm...> - 2012-06-30 20:48:36
|
On Jun 30, 2012, at 3:42 PM, Sandro Tosi <mo...@de...> 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 that we added were minor bugfixes from the release candidate rc2 that you already uploaded. Keep us posted. |
From: Fernando P. <fpe...@gm...> - 2012-06-30 20:47:18
|
On Sat, Jun 30, 2012 at 1:42 PM, Sandro Tosi <mo...@de...> 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 been allowed in at al. Whew :) I hope they'll grant the exception for mpl... Cheers, f |
From: John H. <jd...@gm...> - 2012-06-30 20:54:27
|
On Jun 30, 2012, at 3:46 PM, Fernando Perez <fperez.net@ > > 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. Hopefully he can argue that since r1.1.1-rc2 is already in, they can accept this minor diff to final. If not,Sandro, is there any reason you can't just ship rc2 into debian? It's essentially the same thing. |
From: Fernando P. <fpe...@gm...> - 2012-06-30 20:59:40
|
On Sat, Jun 30, 2012 at 1:54 PM, John Hunter <jd...@gm...> 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, so our diff beta1-HEAD was way too big. We just had to push through the work. Let's just say that my wife was not amused with my Friday night being a non-stop IRC marathon with Min "because we really need to get in before debian freeze tonight!!!" :) f |
From: Sandro T. <mo...@de...> - 2012-06-30 21:36:22
|
Hello, On Sat, Jun 30, 2012 at 10:54 PM, John Hunter <jd...@gm...> 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 the final mpl release doesn't match them, so it's not worth asking for the exception. > If not,Sandro, is there any reason you can't just ship rc2 into debian? It's essentially the same thing. Oh sure, wheezy will release with RC2 - it's just my personal taste to release with the last version :) cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
From: John H. <jd...@gm...> - 2012-06-30 22:05:03
|
On Jun 30, 2012, at 4:35 PM, Sandro Tosi <mo...@de...> 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. |
From: Sandro T. <mo...@de...> - 2012-06-30 22:07:46
|
On Sun, Jul 1, 2012 at 12:04 AM, John Hunter <jd...@gm...> 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, but it must match basic rules, but in this case they are not matched. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
From: Fernando P. <fpe...@gm...> - 2012-06-30 22:09:09
|
On Sat, Jun 30, 2012 at 3:07 PM, Sandro Tosi <mo...@de...> 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 curiosity, what is the mismatch? (I believe you, I just know very little about the debian process). f |
From: Sandro T. <mo...@de...> - 2012-06-30 22:17:59
|
On Sun, Jul 1, 2012 at 12:08 AM, Fernando Perez <fpe...@gm...> wrote: > On Sat, Jun 30, 2012 at 3:07 PM, Sandro Tosi <mo...@de...> 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 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. RC2 will be :) -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
From: Derek H. <de...@as...> - 2012-06-30 23:51:14
|
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. 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 contact us on your own, and you need to contact us soon." Cheers, Derek |
From: John H. <jd...@gm...> - 2012-07-01 00:25:45
|
On Jun 30, 2012, at 6:27 PM, Derek Homeier <de...@as...> 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 contact us on your own, and you need to contact us soon." > > 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. In any care, I apologize for missing the deadline and for the trouble. |
From: Sandro T. <mo...@de...> - 2012-07-01 08:23:07
|
On Sun, Jul 1, 2012 at 2:25 AM, John Hunter <jd...@gm...> 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. Timezones suck :) I need to balance the importance of the update with the additional work the release team will need to carry to accept it (so read another email from someone for a not-so-breaking-the-world update, read the diff, understand it, comment it, reply - it seems few steps, but multiply for all the possible minor updates to debian packages and you'll see) so I think better leave time to deal with the other problems they already have at hand without extra burden. > In any care, I apologize for missing the deadline and for the trouble. Oh don't! there's nothing to be sorry about, it's life and constraints - we're still have a very stable mpl in wheezy, even if the version has a RC in it :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
From: Russell O. <ro...@uw...> - 2012-07-05 16:56:58
|
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 not yet had time to test it on 10.6) localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)" ..K..............KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK..KK.KK.KK.KK.KK.KK.KKK...KK...KK.KK..KKKK..KK.KK.KK.KK.KK.KK..KK.KK.KK.............................................................................F..........................................................................................................KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK.KK...KK.KK.KK.KK.KK.KK.KK.KK..............................................................KK.KK ====================================================================== FAIL: matplotlib.tests.test_mathtext.mathfont_stix_14_test.test ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py", line 36, in failer result = f(*args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/testing/decorators.py", line 140, in do_test '(RMS %(rms).3f)'%err) ImageComparisonFailure: images not close: /Users/rowen/result_images/test_mathtext/mathfont_stix_14.png vs. /Users/rowen/result_images/test_mathtext/expected-mathfont_stix_14.png (RMS 3377.889) ---------------------------------------------------------------------- Ran 1068 tests in 161.293s -- Russell On Jun 9, 2012, at 2: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/ > > As soon as we get binaries, I'll send out another call for testing on > the users list. Russell and Christoph, easiest if you just upload the > binaries directly. You should both have permissions on the sf site. > > A copy of the site docs are available at > http://matplotlib.sourceforge.net/rc/v1.1.1rc2/ |
From: Russell E. O. <ro...@uw...> - 2012-07-05 19:44:08
|
In article <EF3...@uw...>, Russell Owen <ro...@uw...> 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 later) had one unexpected failure on 10.7 (I > have not yet had time to test it on 10.6)... 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, then uploaded it to replace the earlier 10.6 binary. The same test I mentioned in my previous post still fails using the new binary, on both 10.6 and 10.7. -- Russell |
From: John H. <jd...@gm...> - 2012-07-05 19:47:35
|
On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> 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, then uploaded it to replace the earlier 10.6 binary. > > The same test I mentioned in my previous post still fails using the new > binary, on both 10.6 and 10.7. > > Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG. Are you sure you have the requirements on all of the platforms http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements Thanks, JDH |
From: Russell O. <ro...@uw...> - 2012-07-05 19:56:15
|
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 version of Mac OS X I can for the desired binary, but in this case I wanted to see what would happen if I built on 10.7 for a binary that works on 10.6 and 10.7. It resulted in this odd situation: the binary installed everything correctly on 10.7 but somehow failed to install some sub-packages on 10.6. Unfortunately I don't have time to look into it right now; I just took the simple way out of building again on 10.6. Unfortunately that meant a binary with known issues was up for a few hours. I do have the defective binary installer if anyone wants a look at it. -- Russell On Jul 5, 2012, at 12:47 PM, John Hunter wrote: > > > On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> 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, then uploaded it to replace the earlier 10.6 binary. > > The same test I mentioned in my previous post still fails using the new > binary, on both 10.6 and 10.7. > > > Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG. > > Are you sure you have the requirements on all of the platforms > > http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements > > Thanks, > JDH |
From: Russell O. <ro...@uw...> - 2012-07-05 20:44:08
|
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 source. That leaves one unexpected failure with matplotlib 1.1.1 with the 64-bit 10.6-and-later binary and no failures with the 32-bit 10.3.9-and-later binary. Regards, -- Russell On Jul 5, 2012, at 12:47 PM, John Hunter wrote: > On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> 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, then uploaded it to replace the earlier 10.6 binary. > > The same test I mentioned in my previous post still fails using the new > binary, on both 10.6 and 10.7. > > > Almost all of the test failures you ported were 'K' ie KNOWNFAIL. Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG. > > Are you sure you have the requirements on all of the platforms > > http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements > > Thanks, > JDH |
From: Eric F. <ef...@ha...> - 2012-07-05 21:29:55
|
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 dependencies for me to want to try to > build it from source. > > That leaves one unexpected failure with matplotlib 1.1.1 with the 64-bit > 10.6-and-later binary and no failures with the 32-bit 10.3.9-and-later > binary. That one Stix failure is nothing to worry about; it seems there has been some subtle Stix change such that a baseline image that works on one machine fails on another. Eric > > Regards, > > -- Russell > > On Jul 5, 2012, at 12:47 PM, John Hunter wrote: > >> On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw... >> <mailto:ro...@uw...>> 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, then uploaded it to replace the earlier 10.6 binary. >> >> The same test I mentioned in my previous post still fails using >> the new >> binary, on both 10.6 and 10.7. >> >> >> Almost all of the test failures you ported were 'K' ie KNOWNFAIL. >> Usually when you get a bunch of knownfails, it is because you don't >> have a prereq installed, eg inkscape for converting SVG. >> >> Are you sure you have the requirements on all of the platforms >> >> http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements >> >> Thanks, >> JDH > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
From: Jouni K. S. <jk...@ik...> - 2012-07-05 21:34:06
|
Russell Owen <ro...@uw...> 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 want to try to build it from source. The following should help matplotlib find Inkscape: PATH=$PATH:/Applications/Inkscape.app/Contents/Resources/bin \ python -c 'import matplotlib; matplotlib.test(1)' -- Jouni K. Seppänen http://www.iki.fi/jks |
From: Damon M. <dam...@gm...> - 2012-07-06 14:49:43
Attachments:
test_output.txt
|
On Thu, Jul 05, 2012 at 07:43:39PM +0000, Russell E. Owen wrote: > In article <EF3...@uw...>, > Russell Owen <ro...@uw...> 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 later) had one unexpected failure on 10.7 (I > > have not yet had time to test it on 10.6)... > > 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, then uploaded it to replace the earlier 10.6 binary. > > The same test I mentioned in my previous post still fails using the new > binary, on both 10.6 and 10.7. > > -- Russell > I did a git checkout of the v1.1.1 tag and compiled a 64-bit version. I have attached output from the following command: python -c "import matplotlib as m ; m.test(verbosity=1)" Note that some of the tests fail with satuses: KEFKK. I have the following requirements installed: nose: version 1.1.2 PIL: version 1.1.7 ghsotscript: version 9.05 inkscape: 0.48.3.1 All of these were installed using the latest version of macports. Is there anything I can do to improve the output of the tests? -- Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom |
From: Derek H. <de...@as...> - 2012-07-07 20:31:39
|
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, then uploaded it to replace the earlier 10.6 binary. >> >> The same test I mentioned in my previous post still fails using the new >> binary, on both 10.6 and 10.7. >> >> -- Russell >> > > I did a git checkout of the v1.1.1 tag and compiled a 64-bit version. I > have attached output from the following command: > > python -c "import matplotlib as m ; m.test(verbosity=1)" > > Note that some of the tests fail with satuses: KEFKK. > I have the following requirements installed: > > nose: version 1.1.2 > PIL: version 1.1.7 > ghsotscript: version 9.05 > inkscape: 0.48.3.1 > > All of these were installed using the latest version of macports. > Is there anything I can do to improve the output of the tests? I see the same 3 known failures building with fink and the same versions of the above dependencies, and also get the already mentioned Stix failure. Everything else succeeds on 10.5, but I get a different inkscape error on 10.7: +++++ IOError: Conversion command failed: inkscape -z /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2.svg --export-png /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2_svg.png Standard output: Background RRGGBBAA: ffffff00 Area 0:0:720:540 exported to 720 x 540 pixels (90 dpi) Bitmap saved as: /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2_svg.png Standard error: (inkscape:25527): libgnomevfs-WARNING **: Unable to create ~/.gnome2 directory: Permission denied File display/nr-arena-item.cpp line 147 (?): Assertion child->parent == NULL failed ** ERROR:sp-clippath.cpp:308:void sp_clippath_hide(SPClipPath*, unsigned int): code should not be reached Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. ** Message: Error: Inkscape encountered an internal error and will close now. +++++ This is obviously an inscape bug to be reported it to its respective maintainers. I found that on the Inkscape web site 0.48.2 is advertised as the stable release, so I tried downgrading to that version, but just get a similar crash on a different file. Cheers, Derek |
From: Russell E. O. <ro...@uw...> - 2012-07-06 17:38:48
|
In article <m2t...@en...teway>, Jouni K. Seppänen <jk...@ik...> wrote: > Russell Owen <ro...@uw...> 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 want to try to build it from source. > > The following should help matplotlib find Inkscape: > > PATH=$PATH:/Applications/Inkscape.app/Contents/Resources/bin \ > python -c 'import matplotlib; matplotlib.test(1)' Yes, thanks. I figured that out this morning and reran the tests for the 64-bit matplotlib on 10.7. Almost everything passes now. Just a few K and one actual failure that appears to be nothing to worry about (though a failing unit test is always worrisome. I'm still wondering how I managed to build a binary installer that installed the test packages on 10.7 and failed to install them on 10.6, but I don't have time to investigate. -- Russell |