Re: Python only packages and the new Python policy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sergio Talens-Oliag schrieb:
> Hello all,
>
> I was reading the last messages to the list and I've noticed that all python
> packages I have are pure python and I that I could install them for all
> python versions (at least for python >=2.3), but if I install the code on
> /usr/lib/site-python/ the code will only work with the current python
> version and the multiple package solution looks an overkill, as some people
> said.
>
> My proposal for those cases is simple ....
[snipped out]
Hi,
i like that idea. But still, pure Python packages are a minority, and C
extensions have to be built for each Python version. I do not see a simple
solution that can support several Python versions while keeping the overhead of
packages low. And it's not so much about being compatible to older versions of
Python, but to newever ones. Right now, the default Python version is outdated
by quite a time, and quite some people are using 2.4 as a development base right
now. I fear that it'll stay for quite some time now and might happen again in
the future, so supporting only one version of Python might be feasible for
stable, but not for the early adopters and developers using unstable.
greetings
Torsten
- --
Torsten Marek <shlomme@gmx.net>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCyYOhfMVFHqJEyFgRAuoLAJ0UVQX5ltPTNBvbWVEL2TMvAwwWBwCgtXAP
IRjqygP6fYdFGFUGXVctipY=
=xD0Y
-----END PGP SIGNATURE-----
Reply to: