4 ms·
All code WAS written for 2.X, because 3 was either not around yet, under constantly changing flux (before release proper, and to a certain extent for a couple o
by misnome 14y ago
All code WAS written for 2.X, because 3 was either not around yet, under constantly changing flux (before release proper, and to a certain extent for a couple of versions) or the subsequent killer: Not enough libraries that you might depend on, worked in 3.0 yet - as it was written to be deliberately incompatible by removing legacy and old ways of doing things.
IIRC most of the big packages have finally moved over so it'll just become less of an issue over time.
- oracuk 14y agoIs there a clear list anywhere of which major packages have and haven't moved over to Python 3 yet? Edit: I found one here https://python3wos.appspot.com/ https://python3wos.appspot.com/ and another one here http://py3ksupport.appspot.com/ http://py3ksupport.appspot.com/ Looking forward to NLTK 3.0.
- smoyer 14y agoThat's the one I watch ... it's a lot greener today than it was 2 years ago.
- masklinn 14y agoIIRC it became the "Wall of SuperPowers" (from its former Wall of Shame) — indicating more than 50% of tracked packages being P3 compatible — around mid-december 2012.
- oracuk 14y agoThere's been a real change, even from 6 months ago when I last considered Python 3.0. Apart from NLTK (A port is underway) everything I use currently has been ported which was a surprise. Time to start thinking about making the move I think.
- sigzero 14y agoGuido put out a 5 year transition plan. I think we are coming to the tail end of that and now the move is happening to Python 3.