Barry A. Warsaw writes: > I'd dread having to explain to people "this is compatible with Python > Python 2.4.2 but not anything earlier than 2.4.1 unless you're on the > 2.3.x branch and then 2.3.7 is okay, but not 2.3.6 or earlier." Yes; that's a PR pain. I think someone already suggested that when a feature-release series is determined to be "stable" (however that gets defined), a new stable series is started. I.e., if we determine X.Y.Z is stable, it gets released as X.(Y+1), and feature development moves to X.(Y+2). That's pretty much Linux-style as far as I can tell. I don't like the magic interpretation of even/odd, but I can live with that. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4