> hg branches default 85277:4f7845be9e23 2.7 85276:7b867a46a8b4 3.2 83826:b9b521efeba3 3.3 85274:7ab07f15d78c (inactive) 2.6 82288:936621d33c38 (inactive) 3.1 80967:087ce7bbac9f (inactive)
Is it expected that 3.2 is active? Looks like it's been that way a couple months. The branch head: > hg log -r 3.2 changeset: 83826:b9b521efeba3 branch: 3.2 parent: 83739:6255b40c6a61 user: Antoine Pitrou <solip...@pitrou.net> date: Sat May 18 17:56:42 2013 +0200 summary: Issue #17980: Fix possible abuse of ssl.match_hostname() for denial of service using certificates with many wildcards (CVE-2013-2099). Besides that one, there are only two other changesets that would be involved in a merge of 3.2 into default, both having to do with making the 3.2.5 release. As I understand the development docs (and I may be wrong), the intent is that only the default and 2.7 branches should be active at this time. Educate me :-) _______________________________________________ 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
