On Thu, 29 Mar 2012 11:41:46 -0000, "Jason R. Coombs" <jaraco at jaraco.com> wrote: > Does the issue only exist for Python 2.6 and 2.7? It might exist for 3.1 and 3.2 as well. > I'm not familiar with the release process. What's the next step? I would suggest opening an issue on the tracker and marking it as a release-blocker. That way the release managers will see it and can decide what if anything they want to do about it. --David
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