On Sat, Jul 10, 2010 at 1:32 PM, Eric Firing <efir...@hawaii.edu> wrote: > In case anyone working on mpl development missed it, this may be of > interest. I think it's time for us to work seriously on supporting > python 2 and 3 in the same codebase, following numpy's lead. I hope we > can make the transition to git first--and soon. I agree completely. I've looked at our code base ever so briefly in terms of getting setup.py to run. I just committed some changes that work cleanly on both versions and have some more for setupext.py. My problem is that I can't find a way to make setupext.py run clean on both, specifically check_for_tk(). Here we catch the actual exception object and use it to print an error message. If anyone has a suggestion (not print the error? Look at the exception stack?), I'd love to be able to commit these so that at least setup.py runs.
Has anyone looked to see if our other dependencies are ported yet: dateutil, pytz? What about the GUI toolkits? PyQt4 was the only one I found last I looked. Ryan > -------- Original Message -------- > Subject: [Numpy-discussion] ANN: Numpy runs on Python 3 > Date: Sat, 10 Jul 2010 14:30:06 +0000 (UTC) > From: Pauli Virtanen <p...@iki.fi> > Reply-To: Discussion of Numerical Python <numpy-discuss...@scipy.org> > To: numpy-discuss...@scipy.org > > Hi, > > As many of you probably already know, Numpy works fully on Python 3 and > Python 2, with a *single code base*, since March. This work is scheduled > to be included in the next releases 1.5 and 2.0. > > Porting Scipy to work on Python 3 has proved to be much less work, and > will probably be finished "soon". (Ongoing work is here: http:// > github.com/cournape/scipy3/commits/py3k , http://github.com/pv/scipy-work/ > commits/py3k ) > > For those who are interested in already starting to port their stuff to > Python 3, you can use Numpy's SVN trunk version. Grab it: > > svn clone http://svn.scipy.org/svn/numpy/trunk/ numpy > cd numpy > python3 setup.py build > > An important point is that supporting Python 3 and Python 2 in the same > code base can be done, and it is not very difficult either. It is also > much preferable from the maintenance POV to creating separate branches > for Python 2 and 3. We attempted to log changes needed in Numpy at > > http://projects.scipy.org/numpy/browser/trunk/doc/Py3K.txt > > which may be useful (although not completely up-to-date) information for > people wanting to do make the same transition in their own code. > > (Announcement as recommended by our PR department @ EuroScipy :) > > -- > Pauli Virtanen > > _______________________________________________ > NumPy-Discussion mailing list > numpy-discuss...@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
