Matplotlib 1.3.0 was released 1th August. Reproducible: Always
http://matplotlib.1069221.n5.nabble.com/ANN-matplotlib-1-3-0-released-td41670.html
Created attachment 356290 [details] numpydoc ebuild This package is a nightmare. To kick it off, it needs a new package new dep numpydoc which appears to be only py2 compatible. Same deal , 3 days
Created attachment 356294 [details] dev-python/matplotlib/matplotlib-1.3.0.ebuild Fast update : Remove python-3.1 from PYTHON_COMPAT Remove wxwidgets USE flag and always depend on it (Can't get it work without this), also always define "wx = True" in python_configure() Internal copies of pyparsing are now gone, so removed rm from ebuild matplotlib-1.2.0-setup.patch not needed anymore
Created attachment 356296 [details, diff] matplotlib-1.3.0 diff patch This being a demanding package it can do with some more perusing and tinkering. The docs once again need a py2 doc build, the hard coded py2.7 is more or less a place holder for that code that from memory makes a local EPYTHON=ph2.7 and exports it making for the original line to work, or some such. No time limit, go for it
hmm, Bertrand's wxwidgets USE flag distinct to mine but overlooked; a) stipulating SLOT 0 for dateutil (ensures py2&3 compatibility), >=media-libs/libpng-1.2 cited in the INSTALL or some such doc, and b) numpydoc for the doc build which is HUGE. Test suite appears happy which is nice
(In reply to Bertrand Jacquin from comment #3) > Remove wxwidgets USE flag and always depend on it (Can't get it work without > this), also always define "wx = True" in python_configure() Effectively, you are forcing python2 to be enabled unconditionally. This really doesn't make sense to me... how can it work without wxwidgets under python3, but fail under python2?
Created attachment 356302 [details] build.log (In reply to Ian Delaney from comment #5) > hmm, Bertrand's wxwidgets USE flag distinct to mine but overlooked; Using your ebuild (and so with no wxGTK nor wxpython installed) I'm getting the errors attached here # MAKEOPTS=-j1 USE="cairo gtk -doc -examples -excel -fltk -gtk3 -latex -qt4 -tk -wxwidgets" emerge -va1t matplotlib ... Traceback (most recent call last): File "setup.py", line 145, in <module> result = package.check() File "/var/tmp/portage/dev-python/matplotlib-1.3.0/work/matplotlib-1.3.0-python2_7/setupext.py", line 1576, in check wxversion.ensureMinimal('2.8') File "/usr/lib64/python2.7/site-packages/wxversion.py", line 209, in ensureMinimal ImportError: No module named wx
(In reply to Bertrand Jacquin from comment #7) > Created attachment 356302 [details] > build.log > > Using your ebuild (and so with no wxGTK nor wxpython installed) I'm getting > the errors attached here that's fine, that's why I said; 1) this package is a nightmare and 2) This is to kick it off and left it open for more exhaustive testing. It's the week-end but it will get more testing soon
(In reply to Bertrand Jacquin from comment #7) Ah this is interesting; I think pkg_postrm from dev-python/wxpython:2.8 leaves behind /usr/lib/python2.7/site-packages/wxversion.py[co]. If you remove those files, the error should go away.
+*matplotlib-1.3.0 (17 Aug 2013) + + 17 Aug 2013; Mike Gilbert <floppym@gentoo.org> +matplotlib-1.3.0.ebuild: + Version bump, bug 479970. Thanks to Bertrand Jacquin and Ian Delaney.
(In reply to Mike Gilbert from comment #9) > (In reply to Bertrand Jacquin from comment #7) > > Ah this is interesting; I think pkg_postrm from dev-python/wxpython:2.8 > leaves behind /usr/lib/python2.7/site-packages/wxversion.py[co]. If you > remove those files, the error should go away. Right !
