Hi Robert, Robert Bradshaw wrote: > I've been pretty quiet on the P3k stuff, but it looks like things are > coming a long way!
They definitely are. > I'd like to push out another release sometime soon > (next week?)--do you think things will be stable enough to do so by > then? I was already thinking about a new release, too. Having a release out before dev1 would remove the need to keep things releasable while everyone is hacking away. However, there is currently a bit of instability in the C-APIs of Py 2.6 and 3.0. So it would be good, on the other hand, to wait for the final release of the first beta versions, which is scheduled for next week (4th) anyway. That would give us a clean version that compiles code unchanged for Py2.3 through 3.0beta1. If things settle before that, we'll report back to the list. Here's the Py3 release schedule: http://www.python.org/dev/peps/pep-0361/ > (I'd also like to get Dag's new code in.) That shouldn't conflict. Things are pretty much finished, except for the unclear parts of the Py3 C-API. But that's a couple of #defines away. > Sage compiles and runs fine with the current devel branch. Nice. If you feel ambitious, you can try to build it with the last 2.6 alpha. It might not compile with 3.0 right away, but it should not be too hard to get it running on 2.6 for a start. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
