[PyAR2] 2.x or 3.x?
pythonlarry at gmail.com
Sun Jun 28 19:51:03 CEST 2009
I would concur that explaining what works in a pre-3.0 world would be
For most paradigms that I find I use most frequently (but perhaps I'm a
boring coder :), my code works with either version; could a class show ways
and means that work with both standards, pointing out the edge cases where
there's a difference of significance?
I'd be partial to:
Showing what differences there are between 2.x and 3.x; in my
searchings, I have found blurbs and articles that touch on some changes, but
I've not seen much (from a coder's point of view) that's odd, or that I even
_must_ pay attention to. I know I'm missing "it", but am not sure what "it"
For current coders working from pre-3.0, segueing from the above points,
lead nicely into a discussion of 2to3: what it does, what it can't, the
"gotchas", things to manually re-check, etc.
3.x-only coding: In Brief, assume one has never coded in Python before,
ever. What should one know, how "should" one code in this New World Order.
Just my 5 cents. (Inflation)
On Sun, Jun 28, 2009 at 10:52 AM, <paul.hermeneutic at gmail.com> wrote:
> We should prepare people to write in Python 2.x and use 2to3.
> Teaching only 3.x leaves the new developer without many tools. It
> also leaves them less able to understand existing code.
> There will be a time to start with 3.x. Not yet.
> PyAR2 mailing list
> PyAR2 at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the PyAR2