> My plan is to cut a release candidate for 2.3.4 next > Thursday (13th April) Australian time (so Wednesday night > for the merkins), and a release the following Thursday > (the 20th). > > Can we say that the 2.3 branch is frozen from Tuesday? As > this is likely to be the final 2.3 release (modulo any > suprising new bugs), I'd like the time to try and nail > this one. Either you meant May or that mail spent a really long time in some mail queue... ;-) One thing I'd love to see backported to 2.3.4 is the fix to platform.py to properly recognize Windows XP when win32 is detected. Mind if I backport this one personally? --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