> On 25 Mar 2020, at 17:02, Andrew Barnert <abarn...@yahoo.com> wrote: > > On Mar 25, 2020, at 05:02, Paul Moore <p.f.mo...@gmail.com> wrote: >> >> The only reason anyone has ever suggested versioned executables on >> Windows is for Unix compatibility - the reasons they are needed on >> Unix simply don't apply on Windows (at least not in my experience - >> it's possible that some peoplehave workflows that need versioned >> executables, rather than simply using absolute paths or the launcher). > > The obvious exception is exactly the one the OP has: they work primarily in > Cygwin, but use native Windows rather than Cygwin Python, so it’s Cygwin bash > scripts (and Linux-familiar users at the Cygwin shell) launching Python. In > that case, the reasons they’re needed on Unix do apply.
Either a bash alias or a bash script called python3 that runs py.exe with the right args is surely the fix? alias python3='/mnt/c/WINDOWS/py -3' I tested that in cygwin and it works fine. Only odd thing I noticed is that to get a REPL I have to call as "py -3 -i" from cygwin. > However, I’m pretty sure the traditional answer for that use case has always > been to use Cygwin Python, which I’d assume (it’s been nearly a decade since > I’ve dealt with this…) follows the Python-on-Unix naming PEP as well as > whichever linux distro inspires its packaging. Not if you need to get a Windows APIs and services it is not an answer. I think solutions are available without changes to python for the OPs problem. Barry _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/S6KIZCFNOXJM4FKAEBTPBXGAHG4OGRAH/ Code of Conduct: http://python.org/psf/codeofconduct/
