[Python-Dev] check-in policy, trunk vs maintenance branch

Martin v. Löwis martin at v.loewis.de
Mon Nov 3 17:47:12 EST 2003

Alex Martelli <aleaxit at yahoo.com> writes:

> No, but there may be some cases.  E.g., one of the doc fix I proposed (but 
> didn't commit) is to the reference manual, documenting that list 
> comprehensions currently (2.3) "leak" control variables, but code should not
> rely on that since it will be fixed in the future.  That doc fix would not 
> make much sense in 2.4, assuming the leakage will be fixed then, as
> it is currently predicted it will be.

Don't trust predictions. If the patch is formally correct now, apply
it now. If you then find it is not needed a week from now, back it
out. Alternatively, put the patch on SF, wait for a week, and then
apply it to branch only.


More information about the Python-Dev mailing list