Python 3.0 Release
Locked
 
Administrator
|
Just curious: how many of us have tried python 3.0?
http://www.python.org/download/releases/3.0/ .. I ask because a book I'm looking at for teaching python to youngsters jumps right into 3.0: http://www.briggs.net.nz/log/writing/snake-wrangling-for-kids/ -- Owen ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org |
|
|
I thought about it but this Python release is not backwards-compatible and I've got a LOT of v2.5 code. And the migration process (see the bottom of http://docs.python.org/3.0/whatsnew/3.0.html) is not exactly simple...
R P.S. Plus I don't want to recompile numpy and pylab and scipy and... On Thu, Dec 11, 2008 at 10:52 AM, Owen Densmore <[hidden email]> wrote: Just curious: how many of us have tried python 3.0? ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org |
|
Administrator
|
I agree, it certainly won't be without pain.
The suggested way to convert is interesting: • Port to Python 2.6. This should be no more work than the average port from Python 2.x to Python 2.(x+1). Make sure all your tests pass. • (Still using 2.6:) Turn on the -3 command line switch. This enables warnings about features that will be removed (or change) in 3.0. Run your test suite again, and fix code that you get warnings about until there are no warnings left, and all your tests still pass. • Run the 2to3 source-to-source translator over your source code tree. (See 2to3 - Automated Python 2 to 3 code translation for more on this tool.) Run the result of the translation under Python 3.0. Manually fix up any remaining issues, fixing problems until all tests pass again. I asked the sage list about this and their plan is to convert to 2.6 as soon as num/sci py do, then consider the 3.0 change-over. I'm a bit disappointed in their not getting rid of some of the real ugly things in python. Especially not using lexical scoping, and requiring "self" all over the place in variable references. Yes, I want the "self" object reference, but not for instance and class variables. -- Owen On Dec 11, 2008, at 1:44 PM, Robert Holmes wrote: > I thought about it but this Python release is not backwards- > compatible and I've got a LOT of v2.5 code. And the migration > process (see the bottom of http://docs.python.org/3.0/whatsnew/3.0.html) > is not exactly simple... > > R > > P.S. Plus I don't want to recompile numpy and pylab and scipy and... > > On Thu, Dec 11, 2008 at 10:52 AM, Owen Densmore > <[hidden email]> wrote: > Just curious: how many of us have tried python 3.0? > http://www.python.org/download/releases/3.0/ > .. I ask because a book I'm looking at for teaching python to > youngsters jumps right into 3.0: > http://www.briggs.net.nz/log/writing/snake-wrangling-for-kids/ > > -- Owen ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org |
|
|
That strikes me a bit "self"-ish, Owen.
;-} On Thu, Dec 11, 2008 at 2:18 PM, Owen Densmore <[hidden email]> wrote:
-- Doug Roberts, RTI International [hidden email] [hidden email] 505-455-7333 - Office 505-670-8195 - Cell ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org |
«
Return to Friam
|
1 view|%1 views
| Free forum by Nabble | Edit this page |