All, Can anyone shed light on how python 3 is working together with matplotlib, scipy, and numpy? David
All, Now that NumPy is available for python 3.1 and SciPy is well on its way (apparently), are there any plans for matplotlib to be ported? Al
On Tue, Sep 21, 2010 at 8:22 AM, A. S. Budden <ab...@gm...> wrote: > All, > > Now that NumPy is available for python 3.1 and SciPy is well on its > way (apparently), are there any plans for matplotlib to be ported? There are definitely plans; in fact, there's a SVN branch for it. There are no major impediments--the branch can already run a simple example. Unfortunately, development time seems to be quite a lacking resource of late (I *know* it has for me). Patches, however, are always accepted. :) Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma
On 09/21/2010 04:13 PM, Ryan May wrote: > On Tue, Sep 21, 2010 at 8:22 AM, A. S. Budden <ab...@gm...> wrote: > >> All, >> >> Now that NumPy is available for python 3.1 and SciPy is well on its >> way (apparently), are there any plans for matplotlib to be ported? >> > There are definitely plans; in fact, there's a SVN branch for it. > There are no major impediments--the branch can already run a simple > example. Unfortunately, development time seems to be quite a lacking > resource of late (I *know* it has for me). Patches, however, are > always accepted. :) > > Ryan > > Which svn branch? More users ---> more tests and even patches :) Xavier
On Fri, Sep 24, 2010 at 4:45 PM, Xavier Gnata <xav...@gm...> wrote: > On 09/21/2010 04:13 PM, Ryan May wrote: >> On Tue, Sep 21, 2010 at 8:22 AM, A. S. Budden <ab...@gm...> wrote: >> >>> All, >>> >>> Now that NumPy is available for python 3.1 and SciPy is well on its >>> way (apparently), are there any plans for matplotlib to be ported? >>> >> There are definitely plans; in fact, there's a SVN branch for it. >> There are no major impediments--the branch can already run a simple >> example. Unfortunately, development time seems to be quite a lacking >> resource of late (I *know* it has for me). Patches, however, are >> always accepted. :) >> >> Ryan >> >> > Which svn branch? > More users ---> more tests and even patches :) The one called Py3k :) http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/ Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma
On Fri, Sep 24, 2010 at 2:54 PM, Ryan May <rm...@gm...> wrote: > > The one called Py3k :) > > http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/ > In case you want to have ipython while testing, there's already an experimental py3k branch of ipython as well: http://github.com/takowl/ipython/tree/ipy3-newkernel We'll be working with Thomas over the next few months to merge upstream as much of his work as possible, so that we start having decent py3k support in ipython. If you end up helping IPython as well, even better :) Cheers, f
On 09/25/2010 12:02 AM, Fernando Perez wrote: > On Fri, Sep 24, 2010 at 2:54 PM, Ryan May <rm...@gm...> wrote: > >> The one called Py3k :) >> >> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/ >> >> > In case you want to have ipython while testing, there's already an > experimental py3k branch of ipython as well: > > http://github.com/takowl/ipython/tree/ipy3-newkernel > > We'll be working with Thomas over the next few months to merge > upstream as much of his work as possible, so that we start having > decent py3k support in ipython. If you end up helping IPython as > well, even better :) > > Cheers, > > f > I'm not a svn expert but I get an error when I try to checkout the py3k branch: svn: Repository moved temporarily to '/viewvc/matplotlib/branches/'; please relocate Any clues? xavier
On Fri, Sep 24, 2010 at 5:28 PM, Xavier Gnata <xav...@gm...> wrote: > I'm not a svn expert but I get an error when I try to checkout the py3k > branch: > svn: Repository moved temporarily to '/viewvc/matplotlib/branches/'; > please relocate > Any clues? That URL was a link to the web view of SVN. You need to checkout from: svn co https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/branches/py3k Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma
Hi, I have used Matplotlib extensively now for 2 years with python 2.x. I recently needed to move to python 3.1 which was greatly facilitated by numpy and scipy being ported to python 3. I was lucky in that all I have to change is many print statements. All on a Windows OS. But my progress is severely limited by having no port of Matplotlib to python 3. I am definitely a user so have contributed twice to Matplotlib development. Plea: If the stars align properly, I would be so grateful for a port of matplotlib to python 3. Thanks for hearing me.
On 12/23/2010 1:01 PM, Robert Young wrote: > Hi, I have used Matplotlib extensively now for 2 years with python 2.x. > I recently needed to move to python 3.1 which was greatly facilitated by > numpy and scipy being ported to python 3. I was lucky in that all I have > to change is many print statements. All on a Windows OS. > > But my progress is severely limited by having no port of Matplotlib to > python 3. I am definitely a user so have contributed twice to Matplotlib > development. > > Plea: If the stars align properly, I would be so grateful for a port of > matplotlib to python 3. > > Thanks for hearing me. > Did you try the py3k branch at <http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/>? It does work for simple plots. -- Christoph
Thank you for your fast reply and suggestion. I downloaded the GNU tar ball and looked at it. Unfortunately due to my own limitations, I need a win32 installer. I'll have to bide my time I guess. RDY -----Original Message----- From: Christoph Gohlke [mailto:cg...@uc...] Sent: Thursday, December 23, 2010 2:47 PM To: mat...@li... Subject: Re: [Matplotlib-users] Python 3 On 12/23/2010 1:01 PM, Robert Young wrote: > Hi, I have used Matplotlib extensively now for 2 years with python 2.x. > I recently needed to move to python 3.1 which was greatly facilitated by > numpy and scipy being ported to python 3. I was lucky in that all I have > to change is many print statements. All on a Windows OS. > > But my progress is severely limited by having no port of Matplotlib to > python 3. I am definitely a user so have contributed twice to Matplotlib > development. > > Plea: If the stars align properly, I would be so grateful for a port of > matplotlib to python 3. > > Thanks for hearing me. > Did you try the py3k branch at <http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/> ? It does work for simple plots. -- Christoph ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Matplotlib-users mailing list Mat...@li... https://lists.sourceforge.net/lists/listinfo/matplotlib-users
which backend should we use? It does not work with pyqt4 Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.1/dist-packages/pylab.py", line 1, in <module> from matplotlib.pylab import * File "/usr/local/lib/python3.1/dist-packages/matplotlib/pylab.py", line 259, in <module> from matplotlib.pyplot import * File "/usr/local/lib/python3.1/dist-packages/matplotlib/pyplot.py", line 95, in <module> new_figure_manager, draw_if_interactive, show = pylab_setup() File "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/__init__.py", line 25, in pylab_setup globals(),locals(),[backend_name]) File "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4agg.py", line 12, in <module> from .backend_qt4 import QtCore, QtGui, FigureManagerQT, FigureCanvasQT,\ File "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4.py", line 16, in <module> import matplotlib.backends.qt4_editor.figureoptions as figureoptions File "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/figureoptions.py", line 11, in <module> import matplotlib.backends.qt4_editor.formlayout as formlayout File "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/formlayout.py", line 59, in <module> from PyQt4.QtCore import (Qt, SIGNAL, SLOT, QSize, QString, ImportError: cannot import name QString Looks like this backend hasn't been ported yet. Xavier > Thank you for your fast reply and suggestion. I downloaded the GNU tar > ball and looked at it. Unfortunately due to my own limitations, I need > a win32 installer. > I'll have to bide my time I guess. > > RDY > > -----Original Message----- > From: Christoph Gohlke [mailto:cg...@uc...] > Sent: Thursday, December 23, 2010 2:47 PM > To: mat...@li... > Subject: Re: [Matplotlib-users] Python 3 > > > > On 12/23/2010 1:01 PM, Robert Young wrote: >> Hi, I have used Matplotlib extensively now for 2 years with python > 2.x. >> I recently needed to move to python 3.1 which was greatly facilitated > by >> numpy and scipy being ported to python 3. I was lucky in that all I > have >> to change is many print statements. All on a Windows OS. >> >> But my progress is severely limited by having no port of Matplotlib to >> python 3. I am definitely a user so have contributed twice to > Matplotlib >> development. >> >> Plea: If the stars align properly, I would be so grateful for a port > of >> matplotlib to python 3. >> >> Thanks for hearing me. >> > Did you try the py3k branch at > <http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/> > ? It > does work for simple plots. > > -- > Christoph > > ------------------------------------------------------------------------ > ------ > Learn how Oracle Real Application Clusters (RAC) One Node allows > customers > to consolidate database storage, standardize their database environment, > and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
On Sun, Jan 2, 2011 at 12:24 PM, Xavier Gnata <xav...@gm...> wrote: > which backend should we use? > It does not work with pyqt4 > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/local/lib/python3.1/dist-packages/pylab.py", line 1, in > <module> > from matplotlib.pylab import * > File "/usr/local/lib/python3.1/dist-packages/matplotlib/pylab.py", > line 259, in <module> > from matplotlib.pyplot import * > File "/usr/local/lib/python3.1/dist-packages/matplotlib/pyplot.py", > line 95, in <module> > new_figure_manager, draw_if_interactive, show = pylab_setup() > File > "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/__init__.py", line > 25, in pylab_setup > globals(),locals(),[backend_name]) > File > "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4agg.py", > line 12, in <module> > from .backend_qt4 import QtCore, QtGui, FigureManagerQT, > FigureCanvasQT,\ > File > "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4.py", > line 16, in <module> > import matplotlib.backends.qt4_editor.figureoptions as figureoptions > File > "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/figureoptions.py", > line 11, in <module> > import matplotlib.backends.qt4_editor.formlayout as formlayout > File > "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/formlayout.py", > line 59, in <module> > from PyQt4.QtCore import (Qt, SIGNAL, SLOT, QSize, QString, > ImportError: cannot import name QString > > Looks like this backend hasn't been ported yet. I remember seeing this on Gentoo and, unfortunately, never tracked it down. However, it seems to me this is a problem with your PyQt4 install and Python 3, as QString should be found. Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma
On Mon, Jan 3, 2011 at 9:45 AM, Ryan May <rm...@gm...> wrote: > On Sun, Jan 2, 2011 at 12:24 PM, Xavier Gnata <xav...@gm...> wrote: >> which backend should we use? >> It does not work with pyqt4 >> >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> File "/usr/local/lib/python3.1/dist-packages/pylab.py", line 1, in >> <module> >> from matplotlib.pylab import * >> File "/usr/local/lib/python3.1/dist-packages/matplotlib/pylab.py", >> line 259, in <module> >> from matplotlib.pyplot import * >> File "/usr/local/lib/python3.1/dist-packages/matplotlib/pyplot.py", >> line 95, in <module> >> new_figure_manager, draw_if_interactive, show = pylab_setup() >> File >> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/__init__.py", line >> 25, in pylab_setup >> globals(),locals(),[backend_name]) >> File >> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4agg.py", >> line 12, in <module> >> from .backend_qt4 import QtCore, QtGui, FigureManagerQT, >> FigureCanvasQT,\ >> File >> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/backend_qt4.py", >> line 16, in <module> >> import matplotlib.backends.qt4_editor.figureoptions as figureoptions >> File >> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/figureoptions.py", >> line 11, in <module> >> import matplotlib.backends.qt4_editor.formlayout as formlayout >> File >> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/formlayout.py", >> line 59, in <module> >> from PyQt4.QtCore import (Qt, SIGNAL, SLOT, QSize, QString, >> ImportError: cannot import name QString >> >> Looks like this backend hasn't been ported yet. > > I remember seeing this on Gentoo and, unfortunately, never tracked it > down. However, it seems to me this is a problem with your PyQt4 > install and Python 3, as QString should be found. It's not a problem with the PyQt4 installation. PyQt on python-3 uses PyQt's new API, which uses python strings and does not provide QString, QChar, and friends. http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/pyqt4ref.html#selecting-incompatible-apis Darren
On Mon, Jan 3, 2011 at 9:28 AM, Darren Dale <dsd...@gm...> wrote: > On Mon, Jan 3, 2011 at 9:45 AM, Ryan May <rm...@gm...> wrote: >> On Sun, Jan 2, 2011 at 12:24 PM, Xavier Gnata <xav...@gm...> wrote: >>> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/formlayout.py", >>> line 59, in <module> >>> from PyQt4.QtCore import (Qt, SIGNAL, SLOT, QSize, QString, >>> ImportError: cannot import name QString >>> >>> Looks like this backend hasn't been ported yet. >> >> I remember seeing this on Gentoo and, unfortunately, never tracked it >> down. However, it seems to me this is a problem with your PyQt4 >> install and Python 3, as QString should be found. > > It's not a problem with the PyQt4 installation. PyQt on python-3 uses > PyQt's new API, which uses python strings and does not provide > QString, QChar, and friends. > http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/pyqt4ref.html#selecting-incompatible-apis I stand corrected. I don't know what's worse, being so blatently wrong, or having wasted a bunch of time in the past trying to "fix" a "broken" install. Time to don ye olde paper bag... Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma
On 01/03/2011 05:29 PM, Ryan May wrote: > On Mon, Jan 3, 2011 at 9:28 AM, Darren Dale<dsd...@gm...> wrote: >> On Mon, Jan 3, 2011 at 9:45 AM, Ryan May<rm...@gm...> wrote: >>> On Sun, Jan 2, 2011 at 12:24 PM, Xavier Gnata<xav...@gm...> wrote: >>>> "/usr/local/lib/python3.1/dist-packages/matplotlib/backends/qt4_editor/formlayout.py", >>>> line 59, in<module> >>>> from PyQt4.QtCore import (Qt, SIGNAL, SLOT, QSize, QString, >>>> ImportError: cannot import name QString >>>> >>>> Looks like this backend hasn't been ported yet. >>> I remember seeing this on Gentoo and, unfortunately, never tracked it >>> down. However, it seems to me this is a problem with your PyQt4 >>> install and Python 3, as QString should be found. >> It's not a problem with the PyQt4 installation. PyQt on python-3 uses >> PyQt's new API, which uses python strings and does not provide >> QString, QChar, and friends. >> http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/pyqt4ref.html#selecting-incompatible-apis > I stand corrected. I don't know what's worse, being so blatently > wrong, or having wasted a bunch of time in the past trying to "fix" a > "broken" install. > > Time to don ye olde paper bag... > > Ryan > ok. It means that the qt4 backend need to be ported to python3. Should I try the tk backend ? What's the plan? First port matplotlib core? Focus on one backend? What do you want us to test? How should we report python3 related bugs? Xavier