On 4/12/07, David Roe <[EMAIL PROTECTED]> wrote:
>
>
> On 4/12/07, David Roe <[EMAIL PROTECTED]> wrote:
> > I just took a look at the Python 3000 PEP. A couple of points where
> things due to be phased out are commonly used in SAGE:
> > -- raise ValueError, "That number shouldn't be zero" -- now illegal
> > -- raise ValueError("That number shouldn't be zero") -- instead
> >
> > -- print "hello world" -- will become
> > -- print("hello world") -- instead
> >
> > imports will be absolute by default.
> >
> > no more longs. Yay!
> >
> > Classic classes will be gone. I'm not sure what effect this will have,
> but I know that both classic and new classes exist in SAGE.
> >
> > dict.has_key method is disappearing.
> >
> > Defining __cmp__ will no longer make <, ==, > etc work: you have to define
> __richcmp__.
> >
All good points. I have a suggestion: I think it would be worhtwhile
to set up a pybots-like build environment (http://www.pybots.org/) for
SAGE. Basically, pybots is a buildbot that rebuilds your project
everytime a python checkin is made on the trunk. This way you can see
what is breaking and correct it as soon as possible (or complain about
it on python-dev). I think the following components would be vey good
candidates:
* sagex (most important, since it's a modified pyrex only being used by SAGE)
* Ipython
* Mercurial
* numpy
Thoughts? Is this overkill?
didier
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
