This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Tom.N, barry, benjamin.peterson, gvanrossum, orsenthil, pitrou, python-dev
Date 2011-05-20.22:07:33
SpamBayes Score 0.0014373715
Marked as misclassified No
Message-id <>
Let me confirm that. Since it is a security patch the entire point of it is to be placed in the release.

I don't want to question the reasons for doing the release from svn instead of from hg, but I do want to emphasize that the hg branch ought to be considered the master which svn should track as closely as possible.  The only reason to not port a patch to the svn branch would be if it was submitted to the hg branch in contradiction with some policy (e.g. a non-security fix to a branch that should only receive security fixes), and then it should probably be rolled back in the hg branch (and the decision to do so should be very visible on python-dev).
Date User Action Args
2011-05-20 22:07:34gvanrossumsetrecipients: + gvanrossum, barry, orsenthil, pitrou, benjamin.peterson, Tom.N, python-dev
2011-05-20 22:07:33gvanrossumsetmessageid: <>
2011-05-20 22:07:33gvanrossumlinkissue11442 messages
2011-05-20 22:07:33gvanrossumcreate