It'd be helpful to reply in the same thread, rather than starting an unrelated one... On Wed, Nov 28, 2012 at 11:00:04 +0100, Matthias Klose wrote: > I don't think, changes up to 2.7.3-1 need any freeze exception. As I said on irc, they do. > For the other changes: > > - Lib/compiler/consts.py: I'm not aware of code that uses these > constants outside the compile machinery. > ok. > - Lib/mailbox.py: the file descriptor is closed at this point. > sure, you can move the code up, but why does it matter? > I did say it probably doesn't. > - Lib/telnetlib.py: see http://bugs.python.org/issue14635, I would > consider it a bug fix, not a new feature. > Even if I were to accept that, it doesn't qualify unless it's a regression. > - sizeof changes: these are #15512, #15487, #15469, #15424, #15402. > I don't see how correcting the sizeof methods would introduce > regressions. I checked that these are all current sizeof changes, > there are no more on the 2.7 branch. > And I don't see how correcting the sizeof methods in 2.7.3 helps anyone, if 2.6.x and earlier 2.7.x were broken, people will have to handle both cases anyway. > - sysconfigdata.py shouldn't break anything. It even keeps the > internal (starting with an underscore) functions in sysconfig.py, > just avoiding moving the parsing stuff from runtime to buildtime. > ok. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature