On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: > Package: release.debian.org > Severity: normal > User: release.debian.org@packages.debian.org > Usertags: unblock > > Please unblock package python2.7 > So I'm finally getting back to this. There seems to be a lot of changes that are at best a noisy distraction, and not at all appropriate for a freeze exception. Oh well. I don't like the change in Lib/SocketServer.py much, that could easily break stuff as far as I can tell. E.g. if you have a signal handler setting some sort of 'shutdown' flag to do a clean exit, this change means you get into an infinite loop because instead of going back to your main loop you're stuck in the _eintr_retry loop. I guess if we're lucky nobody relied on the typo in Lib/compiler/consts.py... The Tkinter change also seems debatable for a stable branch. I would think Lib/mailbox.py wants to use fstat and fchmod instead of stat/chmod, but I guess that's not a big deal. Why does Lib/multiprocessing/process.py change exitcode when e.args[0] is a string? (it used to be 1, now it's 0) The Lib/telnetlib.py change looks like a new feature rather than a fix. All of the __sizeof__ changes don't seem to be freeze material, unless they're fixing a regression (which seems unlikely). How certain are you that this won't break an assumption somewhere else? debian/patches/sysconfigdata.diff doesn't look like freeze material, how likely is it to break? Cheers, Julien
Attachment:
signature.asc
Description: Digital signature