On Tue, May 29, 2012 at 11:21:37AM +0200, Toni Mueller wrote: > > >After switching python-defaults to python2.7, I'm not sure we discussed > > >whether to keep python2.6 for Wheezy or not. In theory, we should be able > > >to > > >get rid of python2.6 in time for the release (I'd likely be able to act as > > >a > > >driver for the task, as I did for python2.4 and python2.5 tear-down). > > > > > >What do you think? > > > > +1. Time to retire Python 2.6. From Bernd's reply it sounds like the Zope > > upgrade needn't block this. > > please DON'T! > > I am a heavy Zope user, and, as others stated already, the Debian > packages for Zope are useless. Sorry to say it that way, but that's what > it is. This has nothing to do with the way the Zope packagers in Debian > work, just with a gross mismatch of release cycles. > > BUT: > > Having a decent Python2.6 plus assorted packages makes it SO MUCH EASIER > to run Zope on top of Debian, and it actually sets itself apart from the > other platforms with the ease and safety with which you can do this, > currently making Debian one of the, or *the*, most preferrable platform > to deploy Zope. You can make and then support a private repo with python2.6 based on the last Debian release.
> Kicking Python2.6 out of Debian would mean that not only the Zope stuff, > but also the Python core would need to be installed from source code as > well, which makes at least me feel much less comfortable, as I eg. trust > Debian security much more than I trust upstream to not just ignore > Python2.6, thus creating (hard to meet) pressure to move to Python2.7. If you expect official Debian support (including security), that means more work for respective people. The usual question: are you ready to do at least part of that work? -- WBR, wRAR
signature.asc
Description: Digital signature
