Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #98047 > unrolled thread

Re: Python 2 vs Python 3 for teaching

Started byLaura Creighton <lac@openend.se>
First post2015-11-01 15:49 +0100
Last post2015-11-01 15:49 +0100
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.


Contents

  Re: Python 2 vs Python 3 for teaching Laura Creighton <lac@openend.se> - 2015-11-01 15:49 +0100

#98047 — Re: Python 2 vs Python 3 for teaching

FromLaura Creighton <lac@openend.se>
Date2015-11-01 15:49 +0100
SubjectRe: Python 2 vs Python 3 for teaching
Message-ID<mailman.24.1446389385.4463.python-list@python.org>
In a message of Mon, 02 Nov 2015 01:27:24 +1100, Chris Angelico writes:
>On Mon, Nov 2, 2015 at 1:11 AM,  <paul.hermeneutic@gmail.com> wrote:
>> On Nov 1, 2015 2:45 AM, "Chris Angelico" <rosuav@gmail.com> wrote:
>>>
>>> I'm proud to say that a Python tutoring company has just converted its
>>> course over from teaching Python 2.7 to teaching 3.x. For the
>>> naysayers out there, it actually wasn't much of a transition;
>>
>> This would make an excellent opportunity to develop a curriculum to teach
>> students how to maintain a 2.x and 3.x code base using 2to3.
>>
>> 2.x is not going away as fast as some would like.

>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?

Laura

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web