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

2011-01-20 Thread Éric Araujo
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

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

2011-01-20 Thread Barry Warsaw
On Jan 20, 2011, at 05:20 PM, Éric Araujo wrote: This is not relevant to the question about the toolchain that you were asking, but I’d like to point out that importlib in 2.7 is only a subset of the version in 3.1 (precisely, importlib.import_module only), so packaging a full backport of

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

2011-01-20 Thread Jakub Wilk
* Éric Araujo mer...@netwok.org, 2011-01-20, 17:20: I’d like to point out that importlib in 2.7 is only a subset of the version in 3.1 (precisely, importlib.import_module only), so packaging a full backport of importlib makes sense for 2.7 too. python-import is not a full backport of 3.X's

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

2011-01-20 Thread Sandro Tosi
On Thu, Jan 20, 2011 at 17:58, Barry Warsaw ba...@python.org wrote: On Jan 20, 2011, at 05:20 PM, Éric Araujo wrote: This is not relevant to the question about the toolchain that you were asking, but I’d like to point out that importlib in 2.7 is only a subset of the version in 3.1 (precisely,

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

2011-01-20 Thread Barry Warsaw
On Jan 20, 2011, at 07:22 PM, Sandro Tosi wrote: Attention: stupid question coming. Not at all! Would it make sense to rename upstream module to importlib3 (to recall the fact it's a backport from py3k) and so it would importable also in 2.7 along with the stdlib 'importlib' module? I think it

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

2011-01-20 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Barry Warsaw, 2011-01-20 20:26: On Jan 20, 2011, at 07:22 PM, Sandro Tosi wrote: Would it make sense to rename upstream module to importlib3 (to recall the fact it's a backport from py3k) and so it would importable also in 2.7 along with the

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

2011-01-20 Thread Barry Warsaw
On Jan 20, 2011, at 08:55 PM, Michael Fladischer wrote: Barry Warsaw, 2011-01-20 20:26: On Jan 20, 2011, at 07:22 PM, Sandro Tosi wrote: Would it make sense to rename upstream module to importlib3 (to recall the fact it's a backport from py3k) and so it would importable also in 2.7 along with

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

2011-01-19 Thread Sandro Tosi
resending to d-python, probably there's more audience here then on DPMT ml On Wed, Jan 19, 2011 at 20:48, Michael Fladischer mich...@fladi.at wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi team, Following up #606711, I'd like to ask what's the best way to tailor python

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

2011-01-19 Thread Jakub Wilk
* Sandro Tosi mo...@debian.org, 2011-01-19, 23:04: 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