On May 16, 2008, at 1:47 AM, 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?
View it as stable, unstable, and experimental. Also, I view "cython" as where one wants to look to see what's in the latest release. "cython-devel" is new stuff, I try not to commit anything that breaks stuff (to my knowledge) so that there's not much fear of pulling when multiple people are trying to collaborate. "cython-py3" is because it was expected to be broken much(?) of the time. > Also, is there any plans for how one will deal with the split in the > future? Will everything be merged at once, or could the pieces that > are > not py3-specific be merged back before? I think the goal is to try and not let them diverge to much. When py3 is relatively stable, it will get merged into cython-devel. > I'm asking because the > __future__ part will be useful in the devel branch too -- i.e. Greg's > plans for supporting the division statement which would be useful for > Cython as well (if his changes doesn't match Cython code I'll > volunteer > for porting it, it is quite essential for nice NumPy usage...). Yes, certainly. The only reason they're split up is so the (potentially) very broken cython-py3 doesn't interfere with working on cython-devel. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
