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.p
I don't think, changes up to 2.7.3-1 need any freeze exception. For the other
changes:
- Lib/compiler/consts.py: I'm not aware of code that uses these
constants outside the compile machinery.
- Lib/mailbox.py: the file descriptor is closed at this point.
sure, you can move the code up, bu
On Sun, Nov 11, 2012 at 16:23:00 +0100, Julien Cristau wrote:
> 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
On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@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
python2.7/2.7.3-4 now has the upstream fix for the urlparse patch included
(restore the urlparse lists, but use uniform decoding, i.e. don't use the lists
anymore). This should make 2.7.3-4 independent of the other packages migrating
to testing.
python2.7/2.7.3-4 has the breaks to the vim-* packa
On Saturday, July 28, 2012 02:31:50 PM Julien Cristau wrote:
> On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> > As far as I know, the only issue that's come up with the 2.7.3-2 is the
> > urlparse module where they simplified it and dropped some options which
> > gave some package
On Saturday, July 28, 2012 02:31:50 PM Julien Cristau wrote:
> On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> > As far as I know, the only issue that's come up with the 2.7.3-2 is the
> > urlparse module where they simplified it and dropped some options which
> > gave some package
On Saturday, July 28, 2012 02:30:36 PM Julien Cristau wrote:
> On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> > As far as I know, the only issue that's come up with the 2.7.3-2 is the
> > urlparse module where they simplified it and dropped some options which
> > gave some package
On Saturday, July 28, 2012 02:14:04 PM Philipp Kern wrote:
> On Sat, Jul 28, 2012 at 03:39:51AM -0400, Scott Kitterman wrote:
> > My recommendation is that you unblock python2.7, but increase the age
> > requirement to 30 days (it's at 14 righ now) and that you also unblock
> > linkchecker (#682603
On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> As far as I know, the only issue that's come up with the 2.7.3-2 is the
> urlparse module where they simplified it and dropped some options which gave
> some packages a bit of trouble. It appears jwilk did a systematic sweep for
> p
On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote:
> As far as I know, the only issue that's come up with the 2.7.3-2 is the
> urlparse module where they simplified it and dropped some options which gave
> some packages a bit of trouble. It appears jwilk did a systematic sweep for
> p
On Sat, Jul 28, 2012 at 03:39:51AM -0400, Scott Kitterman wrote:
> My recommendation is that you unblock python2.7, but increase the age
> requirement to 30 days (it's at 14 righ now) and that you also unblock
> linkchecker (#682603) and I'll NMU pegasus-wm, createrepo, and gwibber, file
> fore unb
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python2.7
On balance, I think it's better to accept the newer python2.7 than not. I'm
finally motivated to file this bug (instead of randomly hoping jcristau will
fe
13 matches
Mail list logo
