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? > 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. I think these should be user-tagged/tracked with python3/debian-pyt...@lists.debian.org -- 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/535e85e2.3000...@debian.org
