On Mon, Apr 28, 2014 at 12:46 PM, Matthias Klose <d...@debian.org> wrote: > Am 28.04.2014 16:34, schrieb Felipe Sateler: >> On Mon, 28 Apr 2014 14:44:39 +0200, Matthias Klose wrote: >> >>> you are not writing which packages you are talking about ... >>> >>> Am 28.04.2014 12:16, schrieb Osamu Aoki: >>>> python3 support or not (Are we moving too?) >>> >>> bindings and python modules should be built for both Python2 and >>> Python3. If you cannot support both for some reason, please give Python3 >>> the preference. >>> >>> There won't be any "move" to Python3, Python2 will still be in jessie, >>> but people should use Python3 in preference to Python2 if possible. >> >> Today that is not really possible: >> >> felipe@felipepc:tmp% aptitude search '^python3-' | wc -l >> 836 >> felipe@felipepc:tmp% aptitude search '^python-' | wc -l >> 3144 > > sure, how many of the missing ones have upstream python3 support?
No idea. I'm just saying that "move to python3" is not really possible for some use cases today. > >> Just a few weeks ago I decided run a python script for accessing the bts, >> and discovered that you cannot (easily) do it on python3: none of >> reportbug, debianbts or even soappy have python3 support. > > Please file bug reports for these (maybe including patches). I didn't check > soappy, but the others look like Debian upstream packages which should be > ported. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732644 Reportbug uses debianbts, and debianbts in turn uses soappy. So it all depends on either porting soappy (and fpconst, used by soappy) to python3 or porting debianbts away from soappy. Both soappy and fpconst seem dead upstream, which makes option 2 more attractive, but it looks like the soap implementations in python3 do not get along very well with debbugs, as Jordan notes. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAAfdZj8e45iQOw28z40Q=RkEpFaR4B3XVjU6zjDKCrWKcq=4...@mail.gmail.com
