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 <i>know</i> they want to call Python 3.2 instead of Python 3.1...<div>
<br></div><div>Thank you,</div><div>Vlad<br><br><div class="gmail_quote">On Thu, Jul 21, 2011 at 6:07 PM, Éric Araujo <span dir="ltr"><<a href="mailto:merwok@netwok.org">merwok@netwok.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Le 22/07/2011 03:03, Vlad Riscutia a écrit :<br>
<div class="im">> I'm kind of -1 on changing Python executable name. It would make sense for<br>
> different major versions, where there are known incompatibilities, so<br>
> python2-python3 would make sense but python31 python32 not that much...<br>
><br>
> If my team is using Python and it gets pre-installed with other dev-tools,<br>
</div>> do I need to let everyone know they must call python*31*? And if we upgrade,<br>
> make sure everyone knows they should now call python*32*? What if we have<br>
<div class="im">> scripts that call python? Make sure we update all of them whenever minor<br>
> version is changed?<br>
<br>
</div>If I understand correctly, adding versioned filenames like python3.3.exe<br>
would happen in addition of python.exe, not in replacement.<br>
<br>
Regards<br>
</blockquote></div><br></div>