> I agree - there's also the possibility that there will be additional > patches needed to fix a bug in code that's just not relevant for 2.2 > (this is less likely), or an alternate fix might be needed that's > not as thorough as one in 2.2 (where there's a large fix, a smaller > workaround might be more appropriate for 2.1.2) Yup -- this was the case for the profile.py patch (which took a life of its own in 2.2 :-). --Guido van Rossum (home page: http://www.python.org/~guido/)
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