When are we going to get 3toAny2 tools? Python 3 has nice canonical ways to do i18n and byte manipulation, so eventually it will be the preferred way to code. But we will need 3toAny2 tools (because supporting only 2.6 & 2.7 is not realistic)
(Did you know Top-Down parsing rawks? http://effbot.org/zone/simple-top-down-parsing.htm If I begin writing my own 3toAny2 tools, it will be using this technique. I recommend it to anyone who prefers good-ol' coding to playing with grammars and parsers.)
On the flip side some of us authors of packages di...
Anonymous · 2008-11-14T04:30:00
On the flip side some of us authors of packages did the Python 3 port months ago and are just waiting for the final release before we can publish package binaries for the most common operating system out there (Windows) :-)
How about a challenge to folks posting code sample...
Michael Watkins · 2008-11-14T06:42:00
How about a challenge to folks posting code samples, snippets and such on-line: either write it with Python 3 in mind, run 2to3 on it, or point out in posts where issues lurk.
By the way: docutils and Pygments get my vote as two packages that most need porting to 3.0; writing tools ought to be high on the priority list.
@manuelg: I don't know of anyone working on backpo...
Steve · 2008-11-14T07:01:00
@manuelg: I don't know of anyone working on backporting tools; they would be useful, but someone would need to put a lot of work in.
@Anonymous: Glad you are ready!
@Michael Watkins: a good idea. This could be something a lot of people would be interested in.
Don't tell people not to use 3.0 for production us...
Paddy3118 · 2008-11-14T16:46:00
Don't tell people not to use 3.0 for production use. 3.0 will be released in a production ready state. Instead emphasize that support by external packages is beyond your control so users should ensure that any external modules they need are available under 3.0. After all, Python 3.0 comes with batteries included too.
- Paddy.
Generally it's a bad idea to rely on a x.0 version...
James Thiele · 2008-11-14T20:54:00
Generally it's a bad idea to rely on a x.0 version of any software. Python 3.0 hasn't yet been banged on much outside the devs.
Fabio Zadrozny (Mr. Pydev - the Python Eclipse Plu...
manuel moe g · 2008-11-14T02:48:00
Fabio Zadrozny (Mr. Pydev - the Python Eclipse Plug-In) is feeling the pain.http://pydev.blogspot.com/2008/11/pydev-python-30.html
When are we going to get 3toAny2 tools? Python 3 has nice canonical ways to do i18n and byte manipulation, so eventually it will be the preferred way to code. But we will need 3toAny2 tools (because supporting only 2.6 & 2.7 is not realistic)
(Did you know Top-Down parsing rawks? http://effbot.org/zone/simple-top-down-parsing.htm If I begin writing my own 3toAny2 tools, it will be using this technique. I recommend it to anyone who prefers good-ol' coding to playing with grammars and parsers.)
On the flip side some of us authors of packages di...
Anonymous · 2008-11-14T04:30:00
On the flip side some of us authors of packages did the Python 3 port months ago and are just waiting for the final release before we can publish package binaries for the most common operating system out there (Windows) :-)How about a challenge to folks posting code sample...
Michael Watkins · 2008-11-14T06:42:00
How about a challenge to folks posting code samples, snippets and such on-line: either write it with Python 3 in mind, run 2to3 on it, or point out in posts where issues lurk.By the way: docutils and Pygments get my vote as two packages that most need porting to 3.0; writing tools ought to be high on the priority list.
@manuelg: I don't know of anyone working on backpo...
Steve · 2008-11-14T07:01:00
@manuelg: I don't know of anyone working on backporting tools; they would be useful, but someone would need to put a lot of work in.@Anonymous: Glad you are ready!
@Michael Watkins: a good idea. This could be something a lot of people would be interested in.
Don't tell people not to use 3.0 for production us...
Paddy3118 · 2008-11-14T16:46:00
Don't tell people not to use 3.0 for production use. 3.0 will be released in a production ready state. Instead emphasize that support by external packages is beyond your control so users should ensure that any external modules they need are available under 3.0. After all, Python 3.0 comes with batteries included too.- Paddy.
Generally it's a bad idea to rely on a x.0 version...
James Thiele · 2008-11-14T20:54:00
Generally it's a bad idea to rely on a x.0 version of any software. Python 3.0 hasn't yet been banged on much outside the devs.Page 1 of 1
Back to post