Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #98048 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2015-11-02 01:52 +1100 |
| Last post | 2015-11-02 01:52 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python 2 vs Python 3 for teaching Chris Angelico <rosuav@gmail.com> - 2015-11-02 01:52 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2015-11-02 01:52 +1100 |
| Subject | Re: Python 2 vs Python 3 for teaching |
| Message-ID | <mailman.25.1446389566.4463.python-list@python.org> |
On Mon, Nov 2, 2015 at 1:49 AM, Laura Creighton <lac@openend.se> wrote: >>I'd rather not use 2to3 there. If you want to maintain a library that >>can be used from 2.x and 3.x, it's much better to aim for the >>compatible middle - u prefixes on all Unicode strings, b prefixes on >>all byte strings, stick to ASCII where possible, etc, etc. Much easier >>than writing code for one branch and then converting to the other. > > How about using six, same idea with the curriculum? If we were building libraries, then yes, six would be the way to go. But there's really no reason to bother - we're building applications from scratch (or from templates that are under our control), so it's easy to stipulate that Python 3.x is a prerequisite. ChrisA
Back to top | Article view | comp.lang.python
csiph-web