Mark Dickinson <dicki...@gmail.com> added the comment: The new patch looks fine to me.
This is rather last minute for 2.7, and I'm very uncomfortable committing anything substantial this close to the release. Still, if it's really a security vulnerability then it would be good to get it in. For what it's worth, the code looks fine to me, and I've tested thoroughly; I can't see any reasons this could cause problems. Raising priority to release blocker just to alert Benjamin to the issue, and get his permission to go ahead (or not) before the release. ---------- assignee: -> mark.dickinson nosy: +benjamin.peterson priority: normal -> release blocker _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7673> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
