[bobmoretti]

I'm still on Python 2.7. I've built up a lot of infrastructure at work surrounding the "scipy stack".

Are there any major libraries that have not yet been ported to Python 3? I'd be interested to hear about others' experiences making the plunge.

[nilsbunger]

https://python3wos.appspot.com has a list.

boto, fabric, Django (still 'experimental'), and various django packages are my blockers.

gevent also doesn't support python 3.x yet afaik. Can the asyncio stuff supercede it?

[takluyver]

All of the core Scipy Stack is ported, though if you use more specialist libraries, they may be missing. The main pain point in switching is with unicode, which is mostly not an issue for scientific/numberical code. Watch out, though, for integer division: now 1/2==0.5 (not 0).

[analog31]

> Watch out, though, for integer division: now 1/2==0.5 (not 0).

There go half of my bugs. ;-)

[RussianCow]

Twisted is the big one for me. The new async API introduced here sounds really great, but I have so much code built around Twisted that I don't know if it would be worth it for me to switch right away. Maybe I should write my next async project in Python 3.4 and start making a slow transition.

[panzi]

Not a library but I think mercurial currently still only works with Python 2.