Dijkstra on Python
anthony at interlink.com.au
Sat Aug 17 09:03:02 CEST 2002
>>> "James J. Besemer" wrote
> How about the case where a non-upwards-compatible,
> non-bug-fix release N is followed by a release N+1 that
> fixes a bug which happened to be present in release N-1?
Do you have a point here? Can you demonstrate that this has
happened and that's it's caused you problems? Or is this just
pointless bellyaching? Python maintenance releases are _extremely_
carefully done, and the backporting exercise is kept up pretty
solidly. Right now, there are bugs in 2.1.x that have been
fixed in 2.2.x or CVS. Are they serious? No. Serious bugs would
lead to a new 2.1.x release.
If you want to put your hand up and backport every bug fix to
2.1.x, 2.0.x, or even 1.5, great! Please do so. If not, then I
don't see what you're trying to achieve here.
Anthony Baxter <anthony at interlink.com.au>
It's never too late to have a happy childhood.
More information about the Python-list