[Stackless] Policy for taking patches from 2.4?
tismer at stackless.com
Thu Feb 19 13:29:50 CET 2004
Giovanni Bajo wrote:
> Bob Ippolito wrote:
>>There are some potential Python 2.4 features that I *really want to
>>have*. Would it be reasonable for me to merge them into the Stackless
>>2.3.3 branch on a case by case basis, or should I maintain my own
>>version of stackless off-cvs?
> As a general rule, I'd suggest to keep clean trees. If you want 2.4, you can
> create a new branch and port Stackless to it, it shouldn't be too difficult if
> 2.4 development is still ongoing (no clue).
Same here. I agree to back-port patches which are
urgent to have, like real bugs.
For features, I'd prefer to have a 2.4 tree.
It would be nice to have that anyway, since it
would allow us to be ready with the Stackless
port, right after 2.4 is final.
On the other hand, I never figurd out how to
keep stuff in sync, if Python is changed every
I'd be very fond if we had a concept for that!
cheers - chris
Christian Tismer :^) <mailto:tismer at stackless.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
Stackless mailing list
Stackless at stackless.com
More information about the Stackless