View Single Post
Old 09-18-2009, 01:23 PM   #3
ahi
Wizard
ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.
 
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
Quote:
Originally Posted by JSWolf View Post
Python 3 has changed enough so it's not backwards/forwards compatible. All the scripts used to remove DRm won't work with Python 3 and anything you code with Python 3 most likely won't work with 2.5.x or 2.6.x. So basically it's a botch job (IMHO) due to compatibility issues.
I was aware of the purposeful breaking of backwards/forwards compatibility. My question was more aimed at finding out whether people found it difficult to port their Python 2 scripts over to Python 3 and/or whether they found Python 3 easier or harder to program in.

When dealing with Unicode text, I get the impression it ought to be a bit more straightforward... but I fear pitfalls in this still rather young release.

Further clarification: I meant "convert to" in the sense of "converting scripts to", not in the sense of "switching your primary Python installation to". I rather agree with JSWolf that doing so would probably be foolhardy at this time... unless concurrent installations are possible, with Python 2 remaining the default.

- Ahi

Last edited by ahi; 09-18-2009 at 01:26 PM.
ahi is offline   Reply With Quote