From: Fernando G. B. <mo...@gm...> - 2011-02-03 05:13:12
Attachments:
make.osx.diff
|
[Resending in plain text, for better archiving] I stumbled across this post on the matplotlib-users archives (http://www.mailinglistarchive.com/html/mat...@li.../2010-09/msg00359.html) that linked to the py3k branch. After doing a checkout, though, I ran into issues running the make.osx script as the README.osx recommends doing. Since I'm assuming I cannot commit any changes to the branch, let me comment on the few changes that enabled me to compile the dependencies so far. Because I wanted to compile matplotlib for Python 3, I initially changed the 4th line to: PYVERSION=3.1 Apparently urllib changed a bit from python 2 to 3, so I had to change all calls to it to urllib.request, which resulted in the following changes to lines 34-37: ${PYTHON} -c 'import urllib.request; urllib.request.urlretrieve("http://sourceforge.net/projects/libpng/files/zlib/${ZLIBVERSION}/zlib-${ZLIBVERSION}.tar.gz/download", "zlib-${ZLIBVERSION}.tar.gz")' &&\ ${PYTHON} -c 'import urllib.request; urllib.request.urlretrieve("http://sourceforge.net/projects/libpng/files/libpng12/older-releases/${PNGVERSION}/libpng-${PNGVERSION}.tar.gz/download", "libpng-${PNGVERSION}.tar.gz")' &&\ ${PYTHON} -c 'import urllib.request; urllib.request.urlretrieve("http://download.savannah.gnu.org/releases/freetype/freetype-${FREETYPEVERSION}.tar.bz2", "freetype-${FREETYPEVERSION}.tar.bz2")' Note that I also updated the links for zlib and libpng. The original zlib link worked, but I couldn't find the sourceforge project (the url seemed to be old), so I updated it to the one distributed through libpng's project nowadays (which is what the other seems to have been, anyway). For libpng, though, the previous link didn't work and instead of giving an error when downloading, it just created a file that couldn't be uncompressed. Changing these three lines above enabled the download and proper compilation of all deps. I also bumped into a minor typo on line 25, that caused clean not to delete the downloaded libpng tarball: rm -rf zlib-${ZLIBVERSION}.tar.gz libpng-${PNGVERSION}.tar.gz \ After making all these changes, though, the compilation broke when either making mpl_build or mpl_install. Before continuing the debug process, though, I wanted to check with someone knowledgeable of this branch regarding its current status. Is it possible to compile matplotlib on python3? If so, what are the limitations to its capabilities? Thanks so much for your time, -- Fernando P.S.: I'm attaching a diff with all these changes for convenience. |
From: Darren D. <dsd...@gm...> - 2011-02-03 12:48:17
|
On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez <mo...@gm...> wrote: > Before continuing the debug process, though, I wanted to check with > someone knowledgeable of this branch regarding its current status. Is > it possible to compile matplotlib on python3? Mike D. did some initial work for py3 support a while back. I don't know what platform he was working on, but he was able to produce a simple plot, maybe running the simple_plot demo. I understand there is still plenty of work to do, and some of the devs recently discussed it off list. In the next couple of days, I should be able to finish converting the svn/sourceforge repository over to git/github, which will make it easier for some (like me) to contribute to different branches of development. My plan is to rebase the py3k branch so we have a more recent point of reference, and I will probably split the py3k branch into its own repository. I'd like to suggest you clone that repository once it is available, apply your changes in a new branch, and file a pull request on github. Darren |
From: Michael D. <md...@st...> - 2011-02-03 14:05:40
|
On 02/03/2011 07:48 AM, Darren Dale wrote: > On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez > <mo...@gm...> wrote: > >> Before continuing the debug process, though, I wanted to check with >> someone knowledgeable of this branch regarding its current status. Is >> it possible to compile matplotlib on python3? >> > Mike D. did some initial work for py3 support a while back. I don't > know what platform he was working on, but he was able to produce a > simple plot, maybe running the simple_plot demo. > I was working on Linux (RHEL5), and never got past that platform. Mike -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA |
From: Fernando G. B. <fg...@ee...> - 2011-02-03 17:30:53
|
I'll stay on the lookout for the github py3k branch and will do as suggested. Thanks for the update. -- Fernando On Thu, Feb 3, 2011 at 06:05, Michael Droettboom <md...@st...> wrote: > On 02/03/2011 07:48 AM, Darren Dale wrote: >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez >> <mo...@gm...> wrote: >> >>> Before continuing the debug process, though, I wanted to check with >>> someone knowledgeable of this branch regarding its current status. Is >>> it possible to compile matplotlib on python3? >>> >> Mike D. did some initial work for py3 support a while back. I don't >> know what platform he was working on, but he was able to produce a >> simple plot, maybe running the simple_plot demo. >> > I was working on Linux (RHEL5), and never got past that platform. > > Mike > > -- > Michael Droettboom > Science Software Branch > Space Telescope Science Institute > Baltimore, Maryland, USA > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
From: Paul I. <piv...@gm...> - 2011-02-25 23:12:12
|
Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: > On Thu, Feb 3, 2011 at 06:05, Michael Droettboom <md...@st...> wrote: > > On 02/03/2011 07:48 AM, Darren Dale wrote: > >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez > >> <mo...@gm...> wrote: > >> > >>> Before continuing the debug process, though, I wanted to check with > >>> someone knowledgeable of this branch regarding its current status. Is > >>> it possible to compile matplotlib on python3? > >>> > >> Mike D. did some initial work for py3 support a while back. I don't > >> know what platform he was working on, but he was able to produce a > >> simple plot, maybe running the simple_plot demo. > >> > > I was working on Linux (RHEL5), and never got past that platform. > > I'll stay on the lookout for the github py3k branch and will do as > suggested. Thanks for the update. > By the way, there was a recent poll on python.org for packages where users desire Python 3 support. Here are the top 10: Votes | Package ------+-------- 837 | Django 454 | wxPython 406 | scipy 364 | matplotlib 327 | PIL 266 | py2exe 185 | Twisted 179 | PyGTK 135 | Pygame 94 | web2py http://python.org/3kpoll best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 |
From: Benjamin R. <ben...@ou...> - 2011-02-26 00:04:11
|
On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov <piv...@gm...> wrote: > Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: > > On Thu, Feb 3, 2011 at 06:05, Michael Droettboom <md...@st...> > wrote: > > > On 02/03/2011 07:48 AM, Darren Dale wrote: > > >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez > > >> <mo...@gm...> wrote: > > >> > > >>> Before continuing the debug process, though, I wanted to check with > > >>> someone knowledgeable of this branch regarding its current status. Is > > >>> it possible to compile matplotlib on python3? > > >>> > > >> Mike D. did some initial work for py3 support a while back. I don't > > >> know what platform he was working on, but he was able to produce a > > >> simple plot, maybe running the simple_plot demo. > > >> > > > I was working on Linux (RHEL5), and never got past that platform. > > > > I'll stay on the lookout for the github py3k branch and will do as > > suggested. Thanks for the update. > > > > By the way, there was a recent poll on python.org for packages > where users desire Python 3 support. > > Here are the top 10: > > Votes | Package > ------+-------- > 837 | Django > 454 | wxPython > 406 | scipy > 364 | matplotlib > 327 | PIL > 266 | py2exe > 185 | Twisted > 179 | PyGTK > 135 | Pygame > 94 | web2py > > http://python.org/3kpoll > > best, > -- > Paul Ivanov > 314 address only used for lists, off-list direct email at: > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > Which just goes to show that some people don't understand dependencies... (PIL and PyGTK are needed by matplotllib to be fully py3k compatible). Hopefully this will light a fire for them as well. Ben Root |
From: Paul I. <piv...@gm...> - 2011-02-26 00:31:35
|
Benjamin Root, on 2011-02-25 18:03, wrote: > On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov <piv...@gm...> wrote: > > By the way, there was a recent poll on python.org for packages > > where users desire Python 3 support. > > > > Here are the top 10: > > > > Votes | Package > > ------+-------- > > 837 | Django > > 454 | wxPython > > 406 | scipy > > 364 | matplotlib > > 327 | PIL > > 266 | py2exe > > 185 | Twisted > > 179 | PyGTK > > 135 | Pygame > > 94 | web2py > > > > http://python.org/3kpoll > > Which just goes to show that some people don't understand dependencies... > (PIL and PyGTK are needed by matplotllib to be fully py3k compatible). > Hopefully this will light a fire for them as well. Well, this was a user poll - users shouldn't have to know or express all of the dependencies for a given package that they use - that's for us package developers to figure out. To quote from the poll conclusions: What does this poll mean? Off-hand, nothing: nominating a package will not mean that its authors now start porting it to Python 3. However, we still hope that this still has some effect on the Python community: * Volunteers trying to help now see where help is most wanted * Package authors now see that there really is (or is not) demand for getting their package ported. It's that last point that I was trying to highlight for us, as matplotlib was the fourth most nominated package for py3k support. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 |
From: Christoph G. <cg...@uc...> - 2011-02-26 01:01:04
|
On 2/25/2011 4:03 PM, Benjamin Root wrote: > > > On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov <piv...@gm... > <mailto:piv...@gm...>> wrote: > > Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: > > On Thu, Feb 3, 2011 at 06:05, Michael Droettboom <md...@st... > <mailto:md...@st...>> wrote: > > > On 02/03/2011 07:48 AM, Darren Dale wrote: > > >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez > > >> <mo...@gm... <mailto:mo...@gm...>> wrote: > > >> > > >>> Before continuing the debug process, though, I wanted to check > with > > >>> someone knowledgeable of this branch regarding its current > status. Is > > >>> it possible to compile matplotlib on python3? > > >>> > > >> Mike D. did some initial work for py3 support a while back. I don't > > >> know what platform he was working on, but he was able to produce a > > >> simple plot, maybe running the simple_plot demo. > > >> > > > I was working on Linux (RHEL5), and never got past that platform. > > > > I'll stay on the lookout for the github py3k branch and will do as > > suggested. Thanks for the update. > > > > By the way, there was a recent poll on python.org > <http://python.org> for packages > where users desire Python 3 support. > > Here are the top 10: > > Votes | Package > ------+-------- > 837 | Django > 454 | wxPython > 406 | scipy > 364 | matplotlib > 327 | PIL > 266 | py2exe > 185 | Twisted > 179 | PyGTK > 135 | Pygame > 94 | web2py > > http://python.org/3kpoll > > best, > -- > Paul Ivanov > 314 address only used for lists, off-list direct email at: > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > > > > Which just goes to show that some people don't understand > dependencies... (PIL and PyGTK are needed by matplotllib to be fully > py3k compatible). Hopefully this will light a fire for them as well. > > Ben Root > Are PIL and PyGTK holding back matplotlib for Python 3? I have a private port of PIL 1.1.7 for Python 3 that is passing all tests on Windows <http://www.lfd.uci.edu/~gohlke/pythonlibs/#pil> and works well with a couple of other third party libraries (e.g. scipy, biopython). Official Python 3 support is planned for PIL 1.2 <http://mail.python.org/pipermail/image-sig/2011-January/006650.html>. As for PyGTK, there will likely never be an official version for Python 3: "PyGtk 2.24 will be the last release in the PyGtk series. ... New users wising to develop Python applications using GTK are recommended to use the GObject-Introspection features available in PyGObject." <http://mail.gnome.org/archives/gnome-announce-list/2011-February/msg00046.html>. It seems that wxPython, in its current form, will also not be available for Python 3. Python 3 support is planned for the "Next Generation" <http://wiki.wxpython.org/TentativeRoadmap>. There is a private port of wxPython 2.9.x for Python 3 <http://groups.google.com/group/wxPython-dev/browse_thread/thread/49701177b0a72c6f>. I have never gotten it to run reliable. Are there plans for matplotlib to drop Python 2.4 and 2.5? This would make porting to Python 3 much easier. Christoph |
From: John H. <jd...@gm...> - 2011-02-26 02:01:53
|
On Feb 25, 2011, at 7:00 PM, Christoph Gohlke <cg...@uc...> wrote: > Are PIL and PyGTK holding back matplotlib for Python 3 Not at all. Both are optional dependencies. Mpl's hard external dependencies are python, zlib, libpng, freetype and numpy. With those you get the agg, pdf, ps and svg backends. Various GUI tooolkits are optional, as is PIL, which provides some image reading capabilities and image comparisons for the unit tests. |
From: Darren D. <dsd...@gm...> - 2011-02-26 02:31:46
|
On Fri, Feb 25, 2011 at 9:01 PM, John Hunter <jd...@gm...> wrote: > On Feb 25, 2011, at 7:00 PM, Christoph Gohlke <cg...@uc...> wrote: > >> Are PIL and PyGTK holding back matplotlib for Python 3 > > Not at all. Both are optional dependencies. Mpl's hard external dependencies are python, zlib, libpng, freetype and numpy. With those you get the agg, pdf, ps and svg backends. Various GUI tooolkits are optional, as is PIL, which provides some image reading capabilities and image comparisons for the unit tests. Those interested in py3 support should see github.com/matplotlib/matplotlib-py3 and https://github.com/matplotlib/matplotlib-py3/wiki . Mike D. has already made a good start. |
From: Benjamin R. <ben...@ou...> - 2011-02-26 02:54:34
|
On Fri, Feb 25, 2011 at 8:01 PM, John Hunter <jd...@gm...> wrote: > > > > > On Feb 25, 2011, at 7:00 PM, Christoph Gohlke <cg...@uc...> wrote: > > > Are PIL and PyGTK holding back matplotlib for Python 3 > > Not at all. Both are optional dependencies. Mpl's hard external > dependencies are python, zlib, libpng, freetype and numpy. With those you > get the agg, pdf, ps and svg backends. Various GUI tooolkits are optional, > as is PIL, which provides some image reading capabilities and image > comparisons for the unit tests. > While the GUI toolkits are optional, practically speaking, they are a requirement for many (if not most) users. The damn-ing part about the backends is that many users use only one of the GUI backends, and if that one is broken for them, they believe that matplotlib is completely broken. (Evidence: the user who complained that matplotlib was not designed correctly when it turned out that the macosx backend didn't support (non-?)interactive mode). PyGTK not being updated for py3k is a heart-breaker for me. I don't want to even imagine what sort of pain in the butt it is going to be to program using PyGObject introspection (yeah, that sounds like fun...). Ben Root |
From: Eric F. <ef...@ha...> - 2011-02-26 07:37:26
|
On 02/25/2011 04:54 PM, Benjamin Root wrote: > > > On Fri, Feb 25, 2011 at 8:01 PM, John Hunter <jd...@gm... > <mailto:jd...@gm...>> wrote: > > > > > > On Feb 25, 2011, at 7:00 PM, Christoph Gohlke <cg...@uc... > <mailto:cg...@uc...>> wrote: > > > Are PIL and PyGTK holding back matplotlib for Python 3 > > Not at all. Both are optional dependencies. Mpl's hard external > dependencies are python, zlib, libpng, freetype and numpy. With > those you get the agg, pdf, ps and svg backends. Various GUI > tooolkits are optional, as is PIL, which provides some image reading > capabilities and image comparisons for the unit tests. > > > While the GUI toolkits are optional, practically speaking, they are a > requirement for many (if not most) users. > > The damn-ing part about the backends is that many users use only one of > the GUI backends, and if that one is broken for them, they believe that > matplotlib is completely broken. (Evidence: the user who complained > that matplotlib was not designed correctly when it turned out that the > macosx backend didn't support (non-?)interactive mode). > > PyGTK not being updated for py3k is a heart-breaker for me. I don't > want to even imagine what sort of pain in the butt it is going to be to > program using PyGObject introspection (yeah, that sounds like fun...). It's not clear to me how bad it will be to handle this in the mpl backend. This page (http://live.gnome.org/PyGObject/IntrospectionPorting) suggests it might be quite easy, and might not require extensive code change. I think the idea is not so much that the bindings offer a different API but that their implementation is different, they are imported differently, and the constants are different. Unfortunately, the python-gobject package on Ubuntu 10.10 seems to be broken; the example that comes with it won't run. In any case it appears that with the exception of Tkinter, it may take a long time before interactive mpl backends can be used with py3k. Eric > > Ben Root > |
From: Michael D. <md...@st...> - 2011-02-26 12:27:30
|
On 02/26/2011 02:37 AM, Eric Firing wrote: > On 02/25/2011 04:54 PM, Benjamin Root wrote: >> >> On Fri, Feb 25, 2011 at 8:01 PM, John Hunter<jd...@gm... >> <mailto:jd...@gm...>> wrote: >> >> >> >> >> >> On Feb 25, 2011, at 7:00 PM, Christoph Gohlke<cg...@uc... >> <mailto:cg...@uc...>> wrote: >> >> > Are PIL and PyGTK holding back matplotlib for Python 3 >> >> Not at all. Both are optional dependencies. Mpl's hard external >> dependencies are python, zlib, libpng, freetype and numpy. With >> those you get the agg, pdf, ps and svg backends. Various GUI >> tooolkits are optional, as is PIL, which provides some image reading >> capabilities and image comparisons for the unit tests. >> >> >> While the GUI toolkits are optional, practically speaking, they are a >> requirement for many (if not most) users. >> >> The damn-ing part about the backends is that many users use only one of >> the GUI backends, and if that one is broken for them, they believe that >> matplotlib is completely broken. (Evidence: the user who complained >> that matplotlib was not designed correctly when it turned out that the >> macosx backend didn't support (non-?)interactive mode). >> >> PyGTK not being updated for py3k is a heart-breaker for me. I don't >> want to even imagine what sort of pain in the butt it is going to be to >> program using PyGObject introspection (yeah, that sounds like fun...). > It's not clear to me how bad it will be to handle this in the mpl > backend. This page > (http://live.gnome.org/PyGObject/IntrospectionPorting) suggests it might > be quite easy, and might not require extensive code change. I think the > idea is not so much that the bindings offer a different API but that > their implementation is different, they are imported differently, and > the constants are different. Unfortunately, the python-gobject package > on Ubuntu 10.10 seems to be broken; the example that comes with it won't > run. > That's right -- the changes should be minimal. The GObject introspection version is not meant to require the user to perform manual object introspection. The difference is that rather than generating bindings at compile-time (like the old pygtk), the method lookup and resolution happens at run-time (much like Python objects already work). The advantage is there is less of a compilation dependency between the version of pygtk and gtk+, and it should be much easier to get Python access to any library based on GObject. > In any case it appears that with the exception of Tkinter, it may take a > long time before interactive mpl backends can be used with py3k. The Qt4Agg backend is also working (with the exception of the Qt form layout stuff) under Python 3.x. But gtk and cairo will have to wait until the bindings settle down, fltk and Qt 3.x can probably be safely deprecated, and wxPython seems to be in Python 3.x limbo. Mike > Eric > >> Ben Root >> > ------------------------------------------------------------------------------ > Free Software Download: Index, Search& Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |
From: Michiel de H. <mjl...@ya...> - 2011-02-26 12:30:07
|
> In any case it appears that with the exception of Tkinter, it may take a > long time before interactive mpl backends can be used with py3k. The MacOSX backend has already been ported to Py3k (at least the C part of it, which is the largest and most difficult part of it), though I won't be able to test it until the rest of matplotlib has been ported. > The damn-ing part about the backends is that many users use only one of > the GUI backends, and if that one is broken for them, they believe that > matplotlib is completely broken. (Evidence: the user who complained > that matplotlib was not designed correctly when it turned out that the > macosx backend didn't support (non-?)interactive mode). Sometimes I wonder if it is better to retire the MacOSX backend. When it was first introduced, it was much faster (depending on what you wanted to draw) because of how its event loop is organized. By now the other backends use the same event loop strategy, and as far as I know there is no significant difference in speed compared to e.g. the TkAgg backend. The remaining advantage of the MacOSX backend is that it does not rely on other toolkits, and therefore it is easier to compile and use if something changes (e.g., when a new version of OS X comes out, or when compiling for 64-bits, or when Py3K comes out). Still, it needs some maintenance work, and it is hard to keep up. Opinions, anybody? --Michiel. |
From: Jeff W. <js...@fa...> - 2011-02-26 14:11:07
|
On 2/26/11 5:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > The MacOSX backend has already been ported to Py3k (at least the C part of it, which is the largest and most difficult part of it), though I won't be able to test it until the rest of matplotlib has been ported. > >> The damn-ing part about the backends is that many users use only one of >> the GUI backends, and if that one is broken for them, they believe that >> matplotlib is completely broken. (Evidence: the user who complained >> that matplotlib was not designed correctly when it turned out that the >> macosx backend didn't support (non-?)interactive mode). > Sometimes I wonder if it is better to retire the MacOSX backend. When it was first introduced, it was much faster (depending on what you wanted to draw) because of how its event loop is organized. By now the other backends use the same event loop strategy, and as far as I know there is no significant difference in speed compared to e.g. the TkAgg backend. The remaining advantage of the MacOSX backend is that it does not rely on other toolkits, and therefore it is easier to compile and use if something changes (e.g., when a new version of OS X comes out, or when compiling for 64-bits, or when Py3K comes out). Michiel I use the macos x backend almost exclusively, for this reason. It just works! It also supports more output formats than TkAgg. -Jeff > Still, it needs some maintenance work, and it is hard to keep up. > Opinions, anybody? > > --Michiel. > > > > > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search& Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |
From: Eric F. <ef...@ha...> - 2011-02-26 18:06:07
|
On 02/26/2011 02:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > > The MacOSX backend has already been ported to Py3k (at least the C part of it, which is the largest and most difficult part of it), though I won't be able to test it until the rest of matplotlib has been ported. > >> The damn-ing part about the backends is that many users use only one of >> the GUI backends, and if that one is broken for them, they believe that >> matplotlib is completely broken. (Evidence: the user who complained >> that matplotlib was not designed correctly when it turned out that the >> macosx backend didn't support (non-?)interactive mode). > > Sometimes I wonder if it is better to retire the MacOSX backend. When it was first introduced, it was much faster (depending on what you wanted to draw) because of how its event loop is organized. By now the other backends use the same event loop strategy, and as far as I know there is no significant difference in speed compared to e.g. the TkAgg backend. The remaining advantage of the MacOSX backend is that it does not rely on other toolkits, and therefore it is easier to compile and use if something changes (e.g., when a new version of OS X comes out, or when compiling for 64-bits, or when Py3K comes out). Still, it needs some maintenance work, and it is hard to keep up. > Opinions, anybody? Michiel, I don't have a mac, so I can't say yes or no based on my own usage. Your efforts in writing and maintaining that backend are appreciated, though. What about the non-interactive mode behavior--is it hard to make the MaxOSX backend behave like the others in that respect? From the general developer standpoint, I don't like divergence in behavior among the backends. (I don't even like the way QT4agg seems to be diverging.) Eric > > --Michiel. |
From: Michiel de H. <mjl...@ya...> - 2011-02-27 02:25:43
|
--- On Sat, 2/26/11, Eric Firing <ef...@ha...> wrote: > What about the non-interactive mode behavior--is it hard to > make the MaxOSX backend behave like the others in that > respect? I agree that this should be done, but I just haven't found the time to look at it (recently I have been looking at getting animations to work with the MacOSX backend). Probably it is not all that hard, and I would welcome contributions from other developers who use the MacOSX backend to get the non-interactive mode behavior consistent with the other backends. On a related note, something I found confusing for new matplotlib users is that after first installing it, matplotlib is non-interactive by default. After installing matplotlib, I think users should be able to try it out and make some simple plots that appear on the screen without having to find out about interactive behavior and edit matplotlibrc. Especially people that are new to programming or to Python may be disappointed if their first plotting attempts don't seem to produce a figure. --Michiel. |
From: Eric F. <ef...@ha...> - 2011-02-27 07:07:02
|
On 02/26/2011 04:25 PM, Michiel de Hoon wrote: > --- On Sat, 2/26/11, Eric Firing<ef...@ha...> wrote: >> What about the non-interactive mode behavior--is it hard to >> make the MaxOSX backend behave like the others in that >> respect? > I agree that this should be done, but I just haven't found the time to look at it (recently I have been looking at getting animations to work with the MacOSX backend). Probably it is not all that hard, and I would welcome contributions from other developers who use the MacOSX backend to get the non-interactive mode behavior consistent with the other backends. > > On a related note, something I found confusing for new matplotlib users is that after first installing it, matplotlib is non-interactive by default. After installing matplotlib, I think users should be able to try it out and make some simple plots that appear on the screen without having to find out about interactive behavior and edit matplotlibrc. Especially people that are new to programming or to Python may be disappointed if their first plotting attempts don't seem to produce a figure. That's a good point. Until fairly recently, interactive behavior worked across backends only via ipython magic, so I think the non-interactive default had a solid historical rationale. Now, however, we could probably make interactive mode the startup default for interactive backends without causing any problems. I agree that this would be more intuitive and more familiar to people coming from matlab. Eric > > --Michiel. |
From: John H. <jd...@gm...> - 2011-02-27 13:49:26
|
On Sun, Feb 27, 2011 at 1:06 AM, Eric Firing <ef...@ha...> wrote: > That's a good point. Until fairly recently, interactive behavior worked > across backends only via ipython magic, so I think the non-interactive > default had a solid historical rationale. Now, however, we could > probably make interactive mode the startup default for interactive > backends without causing any problems. I agree that this would be more > intuitive and more familiar to people coming from matlab. Probably right -- this was a design decision made early on when I did not see a good way around the problem that the idle drawing across backends now solves. There will probably be some unintended consequences of changing the default, but as long as we document it prominently and provide a way for people to change the behavior to the old wan in their rc, it is probably a good idea to make this change. |
From: Matthew B. <mat...@gm...> - 2011-02-26 18:12:27
|
Hi, On Sat, Feb 26, 2011 at 4:30 AM, Michiel de Hoon <mjl...@ya...> wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > > The MacOSX backend has already been ported to Py3k (at least the C part of it, which is the largest and most difficult part of it), though I won't be able to test it until the rest of matplotlib has been ported. > >> The damn-ing part about the backends is that many users use only one of >> the GUI backends, and if that one is broken for them, they believe that >> matplotlib is completely broken. (Evidence: the user who complained >> that matplotlib was not designed correctly when it turned out that the >> macosx backend didn't support (non-?)interactive mode). > > Sometimes I wonder if it is better to retire the MacOSX backend. When it was first introduced, it was much faster (depending on what you wanted to draw) because of how its event loop is organized. By now the other backends use the same event loop strategy, and as far as I know there is no significant difference in speed compared to e.g. the TkAgg backend. The remaining advantage of the MacOSX backend is that it does not rely on other toolkits, and therefore it is easier to compile and use if something changes (e.g., when a new version of OS X comes out, or when compiling for 64-bits, or when Py3K comes out). Still, it needs some maintenance work, and it is hard to keep up. > Opinions, anybody? Seconding Jeff - I use the MacOSX backend too - was very grateful not to have to install the other toolkits or suffer ugliness. So, I'm also grateful... Best, Matthew |
From: Michael D. <md...@st...> - 2011-02-26 12:31:41
|
On 02/25/2011 08:00 PM, Christoph Gohlke wrote: > > On 2/25/2011 4:03 PM, Benjamin Root wrote: >> >> On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov<piv...@gm... >> <mailto:piv...@gm...>> wrote: >> >> Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: >> > On Thu, Feb 3, 2011 at 06:05, Michael Droettboom<md...@st... >> <mailto:md...@st...>> wrote: >> > > On 02/03/2011 07:48 AM, Darren Dale wrote: >> > >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez >> > >> <mo...@gm...<mailto:mo...@gm...>> wrote: >> > >> >> > >>> Before continuing the debug process, though, I wanted to check >> with >> > >>> someone knowledgeable of this branch regarding its current >> status. Is >> > >>> it possible to compile matplotlib on python3? >> > >>> >> > >> Mike D. did some initial work for py3 support a while back. I don't >> > >> know what platform he was working on, but he was able to produce a >> > >> simple plot, maybe running the simple_plot demo. >> > >> >> > > I was working on Linux (RHEL5), and never got past that platform. >> > >> > I'll stay on the lookout for the github py3k branch and will do as >> > suggested. Thanks for the update. >> > >> >> By the way, there was a recent poll on python.org >> <http://python.org> for packages >> where users desire Python 3 support. >> >> Here are the top 10: >> >> Votes | Package >> ------+-------- >> 837 | Django >> 454 | wxPython >> 406 | scipy >> 364 | matplotlib >> 327 | PIL >> 266 | py2exe >> 185 | Twisted >> 179 | PyGTK >> 135 | Pygame >> 94 | web2py >> >> http://python.org/3kpoll >> >> best, >> -- >> Paul Ivanov >> 314 address only used for lists, off-list direct email at: >> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 >> >> >> >> Which just goes to show that some people don't understand >> dependencies... (PIL and PyGTK are needed by matplotllib to be fully >> py3k compatible). Hopefully this will light a fire for them as well. >> >> Ben Root >> > > Are PIL and PyGTK holding back matplotlib for Python 3? PIL is used for the regression test framework, but it should be possible to remove that dependency there by using our own png loading code. PyGTK is optional, of course, and users can use another GUI backend until the pygtk bindings catch up. > Are there plans for matplotlib to drop Python 2.4 and 2.5? This would > make porting to Python 3 much easier. Yes. The minimum version for this Python 3.x compatibility work is Python 2.6. Anything earlier is just insane ;) Mike > > Christoph > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search& Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |