[Python-modules-team] Dependencies for python2.6-only packages (best practice)

[Michael Fladischer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi team,

Following up #606711, I'd like to ask what's the best way to tailor
python dependencies for a package when it's content is a backport of a
future Debian default python (e.g. 2.7) feature?

In the case of importlib, it's inclusion in upstream python started with
2.7 but I'd like to provide the backport for at least 2.6.

python-support translates "XS-Python-Version: 2.5,2.6" into "python (<<
2.7)" for ${python:Depends}, so once 2.7 becomes the default for Debian,
importlib would no be installable for python2.6.

Matthias Klose came up with patching ${python:Depends} during build.
After a conversation with Sandro Tosi we came up with omitting
${python:Depends} and defining the dependencies manually like this:
"python2.6 | python2.5".

Is there a better way to do this with python-support?

And as a accompanying question: Does it make sense to still support
python2.5?

Thanks for your help,
- -- 
Michael Fladischer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk03QCIACgkQeJ3z1zFMUGZ7hACfdxigEmrody/kK46im8qTfQBI
oBUAnjHqTASVLXeeezXMOR4wyAPUnzim
=v0T5
-----END PGP SIGNATURE-----