RetroSearch Browse

Fri Jul 22 03:07:31 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-July/112460.html

Hi,

Le 22/07/2011 03:03, Vlad Riscutia a écrit :
> I'm kind of -1 on changing Python executable name. It would make sense for
> different major versions, where there are known incompatibilities, so
> python2-python3 would make sense but python31 python32 not that much...
> 
> If my team is using Python and it gets pre-installed with other dev-tools,
> do I need to let everyone know they must call python*31*? And if we upgrade,
> make sure everyone knows they should now call python*32*? What if we have
> scripts that call python? Make sure we update all of them whenever minor
> version is changed?

If I understand correctly, adding versioned filenames like python3.3.exe
would happen in addition of python.exe, not in replacement.

Regards

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112460.html below:

[Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)