Hi Thomas (2011.10.03_12:15:04_+0200) > > > It looks like python2.7 is easily backporteable to squeeze. > Good news! :)
Of course most other upstreams that want their code to run on an existing server install, with minimal hassle, support Python 2.6 or even 2.5. The enterprise distributions move *very* slowly. I know of people complaining that their deployment environment only has 2.4... > Well, if I understood it right, it is mostly recompiling / repackaging > the current stuff from wheezy. That would be required to fix some bugs (wheezy doesn't even have 2.7 as default yet, but that'll happen in the next week or so). Many packages will support 2.7, but some of them will need to be rebuilt to support it (i.e. C extensions, or packages using dh_python2) I suspect that such rebuilding probably couldn't happen in Debian's backports, as it would impact many packages. > > > I can help with that but you have to find a DD willing to upload this > > > backport. > OK, any DD here willing to review / help with this? You actually need someone on the backports team. > > Backporting python2.7 by itself probably won't help you that much. You'll > > also need to backport/update python-defaults > What's "python-defaults"? I could not find a file or package with that > name. python-defaults is a source package. It builds the "python" package, "python-all", etc. This determines what verions of python are available and supported. If you were to add 2.7 as a supported version, you'd have to touch python-support and python-central as well. They hardcode supported python versions. And before you could do that, you'd need to ensure that every pure-python module is 2.7-compatible or has XS-Python-Version: << 2.7 (or equivalent) in the source package. Or you'd run into bugs like these: http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=python2.4-incompatible&user=debian-python%40lists.debian.org > I guess I would only care for very few packages, primarily virtualenv. > Because if you have that, you can install what you need into a virtual > env. virtualenv uses python-support, so to get it to work under 2.7, you'd have to change python-support, which means everything else using python-support would have to be 2.7 compatible. Maybe I'm being overly pessimistic, but this sounds like an impossibly big task for doing properly in debian-backports. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111003113004.gz6...@bach.rivera.co.za
