On Thu, 29 Mar 2012 11:41:46 -0000, "Jason R. Coombs" <jar...@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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
