On Tue, Apr 15, 2008 at 2:23 PM, Charles R Harris <[EMAIL PROTECTED]> wrote:
> > > On Tue, Apr 15, 2008 at 1:21 PM, Bruce Southey <[EMAIL PROTECTED]> wrote: > > > Hi, > > You probably should start with the 2to3.py tool (see link at > > http://www.python.org/download/releases/3.0/). > > > > Looks like a lot of the changes aren't at all backward compatible. The new > style print, for instance, doesn't work with the older versions of python. > So it looks like like we will have to fork the trunk and also decide on when > to release a Python3.0 version and how long to maintain support for the > earlier versions. I think the best thing to do is release a numpy version, > say 1.2, as bug free as we can and with few API changes, put it in > maintenance mode, and move on to 3.0 with a release that is a simple > adaption without API changes. > Oh, and making the transition will be made a lot easier by having a complete set of tests. Getting the tests and documentation into good state might be the best focus for our 1.2 effort. Chuck
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
