OK then. I don't have a *strong* opinion against it, just thought that most people have one version of Python, maybe 2 versions as in 2.x and 3.x, so I would understand python2.exe, python3.exe but yeah, it's not that big of a deal either way.
Thank you, Vlad On Fri, Jul 22, 2011 at 6:41 AM, Brian Curtin <brian.cur...@gmail.com>wrote: > On Thu, Jul 21, 2011 at 20:30, Vlad Riscutia <riscutiav...@gmail.com>wrote: > >> If versioned filenames are added in addition to python.exe, it still might >> look confusing for most users: Why do I have python and python3.2 >> executables? What's the difference? I'd rather go with -v argument either >> way, for people that *know* they want to call Python 3.2 instead of >> Python 3.1... >> >> Thank you, >> Vlad >> > > Honestly, would it really be that confusing? Seeing python32.exe inside > C:\Python32 shouldn't be a huge surprise, and ActiveState has been doing > something like this for years (forever?). > > Versioned executables in addition to the standard python.exe is something > I've wanted for a while, but that's outside of this PEP. This way you could > have C:\Python27 and C:\Python32 on your path and explicitly open up the > right one. >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
