Il 18/06/2010 14.37, Scott Kitterman ha scritto: > XS-Python-Version: >= 2.x > XS-Python3-Version: >= 3.x > > This avoids any risk of existing packages inadvertently expressing support > for > a Python3 version, but adds more fields to debian/control (this would also > imply, I think, XB-Python3-Version). This ends up making Packages.gz (and > .bz2) larger and making updates slower for everyone.
I'd prefer this method over the above, it's clear and there's less risk to inadvertitely support python3 without proper source changes. Size is not that important: adding 30 bytes to 3,000 packages is less than 100Kb unzipped in total size, not a big deal after all. > Related points: Python policy already says "all" means all Python2 versions > and has no meaning in a Python3 context and that "current" is deprecated and > does not apply at all to Python3. Agreed. Changing "all" to include support to python3 is dangerous. I once read that almost 90% of the code needs at least basic porting. Regards, -- .''`. : :' : Luca Falavigna <dktrkr...@debian.org> `. `' `-
signature.asc
Description: OpenPGP digital signature
