> Two questions wrt 2.2.1: > > - Is there a timeline for it? I couldn't find one in PEP251 (which > stops at 2.2 final). The reason I ask is that there's a serious flaw > in MacPython (has been there since day one) that renders it useless on > multiprocessor Mac OS X machines. I'm waiting for an external party to > fix this (as the problem is in an external library), but I could put a > bit of pressure on if 2.2.1 is due reasonably soon (as I hope). No timeline -- that sort of depends on how many really bad bugs are reported, and whether someone volunteers as a release mananger. > - The final bits of the Mac tree havne't been checked in yet, should > we move the release22-maint branch when that's done? Can you move a > branch? How? Fred anticipated that; he said he would just move the tags when necessary. Don't worry about it. --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