Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!newsfeed.tele2net.at!news.panservice.it!feed.xsnews.nl!border02.ams.xsnews.nl!feeder04.ams.xsnews.nl!abp002.ams.xsnews.nl!frontend-F09-05.ams.news.kpn.nl
From: Cecil Westerhof <Cecil@decebal.nl>
Newsgroups: comp.lang.python
Subject: Re: l = range(int(1E9))
Organization: Decebal Computing
References: <87k2wtvbx1.fsf@Equus.decebal.nl> <mailman.135.1430413555.3680.python-list@python.org> <mhtnpg$fsf$1@dont-email.me> <87mw1ptpr0.fsf@Equus.decebal.nl> <mailman.146.1430427228.3680.python-list@python.org> <mhu6df$6bs$2@dont-email.me> <CAPTjJmrs=a=L9TiRUnBPs561bEQFsoBv+3oaQmez5Yi-1gEW6A@mail.gmail.com> <mailman.152.1430435562.3680.python-list@python.org>
X-Face: "(y8cC@tg_12{">GF'UXTW]FHI2wMiZNrnf'1EFQ&O#$m:f#O7+7}kR<J%a^F2lh4[N~Yz4 nSp#c+aQo1b5=?HcNEkQ7QzF<])O3X4MDL/AYjys&*mt>,v+Pti8=Vi/Z"g^?b"E
X-Homepage: http://www.decebal.nl/
Date: Fri, 01 May 2015 07:04:22 +0200
Message-ID: <87383gsxbd.fsf@Equus.decebal.nl>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:77uuheIr0BuymjnoQaxeydeA4oE=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Lines: 32
NNTP-Posting-Host: 81.207.62.244
X-Trace: 1430457292 news.kpn.nl 19737 81.207.62.244@kpn/81.207.62.244:42692
Xref: csiph.com comp.lang.python:89695

Op Friday 1 May 2015 01:12 CEST schreef Ben Finney:

> Chris Angelico <rosuav@gmail.com> writes:
>
>> Very easily and simply: Python 3 and Python 2 will always install
>> separately, and the only possible conflicts are over the "python"
>> command in PATH and which program is associated with ".py" files.
>
> Calling ‘python’ is now ambiguous, and with Python 2 slipping
> inexorably into the past, increasingly the ‘python’ command is the
> wrong choice for code that we want to survive in the future.
>
> I am seeing a growing call, with which I agree, to recommend
> explicitly calling ‘python2’ or ‘python3’ as commands.
>
> That includes when we type it for direct invocation, or when we set
> it as the command for automatic execution of a program (e.g. in the
> “shebang” line of a program).
>
> Use the command ‘python2’ or ‘python3’ to be explicit about which
> Python version you intend to run.

Good tip. I used python and python3, but there is also a python2. I
learn myself to use that instead of python.

By the way: I also see python3.4 and python3.4m. Any idea where the m
stands for?

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof