Martin v. Löwis wrote: > Neal Norwitz wrote: >> Should we plan to put out a final 2.5 release? If so, should we >> continue to backport fixes (like Martin's removal of Alpha in >> setup.py)? My preference is that we do put out a final 2.5 that has >> all accumulated bug fixes. Then close the branch. That way if we put >> out a security release for 2.5, it will be clean and easy. > That is my plan also. I would like to release 2.5.2 two weeks after > Python 3.0, or on November 1st, whatever happens later (and it seems > that Python-3-plus-two-weeks happens later). You of course meant 2.5.3.
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