When should Python 3.3 become the default?

[Matthias Klose]

On 20.10.2012 23:34, Dmitrijs Ledkovs wrote:
> I took a stab at the transition tracker:
> http://people.canonical.com/~ubuntu-archive/transitions/python3.3.html
> 
> It does not look that bad. Locally (newer transition tracker ;-) ) it
> tells me 120 arch:all packages & 90 arch:any source packages.
> It's not a tiny transition but not that large either.

here's the list of architecture dependent python3 modules, which need looking at
for raring. I did look at ones with interesting build systems.

 - pygobject (autoconf based) installs extensions without a
   proper abi tag. the renaming in the packaging was broken.

 - py3cairo's waflib build system does safe information out of
   build dir, again, fixed in the packaging (and did need a 3.3
   fix too).

Others like python-apt using distribute just die because of missing 3.3
compatibility.

The list may contain packages which only build for the the default python
version, however this cannot be seen by just looking at the metadata.

apparmor
brltty
cracklib2
dbus-python
distro-info
gearman-interface
jinja2
liblouis
lxc
markupsafe
mpi4py
newt
postgresql-9.1
psycopg2
py3cairo
pycurl
pyepr
pyfits
pyicu
pykde4
pyopenssl
py-postgresql
pyside
pystemmer
python-apt
python-bitarray
python-bsddb3
python-crypto
python-cups
python-drizzle
python-leveldb
python-llfuse
python-numpy
python-pam
python-pylibacl
python-pyxattr
python-qt4
python-regex
python-scipy
python-smbc
pyyaml
pyzmq
qscintilla2
sip4
speech-dispatcher
sqlalchemy
subunit
urwid
uwsgi
virtkey
yp-svipc
zope.interface