Anthony Baxter writes: > > >>> "Raymond Hettinger" wrote > > After closing a bug report for something fixed in Py2.2.3 and beyond, > > I later wondered if it should be left open so that a fix can be made back > > to Py2.1.4. > > > > My question is whether there is going to be another bugfix release > > for 2.1 or can we limit our open bugs and backports to just 2.2? > > > > My own preference is to avoid considering 2.1 because the issues > > and solutions tend to change as you go back in time. > > My own opinion (as someone who's been down this path before) is that > another 2.1.x release is only worthwhile if a sufficiently vile bug > crops up in a way as to cause serious problems (as the GC and > trashcan bugs did for 2.1.2/2.1.3). there is the security related fix for os.py (_execvpe), which is in CVS, but not in a released 2.1.x. And a major application (zope) still requires 2.1.x. Matthias
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