Hi folks As you might have just noticed, we have now dropped the Python 2 module package (python-debian) from the archive. I've not yet disabled running the test suite under Python 2 on salsa.
The question is then what to do with Python 2 support and indeed also code that exists to work around limitations in Python 3.3 and 3.4. We can do one of the following: 1) Continue to support python >= 2.7 and python3 >= 3.3. Leave the Python 2 and 3.old code in there for the time being and leave the test suite running under Python 2 for as long as possible. However, the tests are run against Debian unstable and python-apt will soon be unavailable there. 2) Continue to support python >= 2.7 and python3 >= 3.3. Leave the Python 2 and 3.old code there with disabled tests and when it breaks, shrug our shoulders 3) Declare support for python3 >= 3.5. Disable tests but only remove the legacy support whenever someone is spending time on a particular piece of code 4) Declare support for python3 >= 3.5. Actively remove old code now. Thinking about releases we support, python3 in stretch and all supported Ubuntu releases is >= 3.5. Any backported packages that needed a newer python- debian for some reason would also be using python3 >= 3.5 at this stage. I am personally leaning towards 3 or 4. Comments and suggestions most welcome. Stuart -- Stuart Prescott http://www.nanonanonano.net/ [email protected] Debian Developer http://www.debian.org/ [email protected] GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-python-debian-maint
