Hi, Dag Sverre Seljebotn wrote: >> Sorry, that was a bug. It should have been done the way you proposed (that's >> the moments when I'm happy to work on a branch and not on cython-devel). > > (This is not retorical, I want to ask and learn about how the repos > should be used:) > > Isn't the "cython" branch where releases are pulled from? Would a > temporary bug (fixed one day later) in cython-devel matter, isn't that > just a consequence of it being a devel branch? And what are the > differences between devel-py3 and devel in this respect?
The cython-devel-py3 branch was very unstable over the last few days. Since cython-devel is the main development branch, it's ok for it to be "under development", but it's not ok if it's broken. (That said, changes that get pushed to the public server should never break whatever branch they appear in. My bad...) > Also, is there any plans for how one will deal with the split in the > future? I'm planning to merge the changes ASAP, but I'd like to fix the "print" statement for Py3 first, as there are currently a lot of test cases that fail because of that, so this may actually hide real bugs. BTW, in Py3, "print" will simply call the print function. The tricky thing is to generate the cleanup code correctly for the two code branches that the C preprocessor selects in Py2 and Py3... Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
