On Mar 25, 2020, at 05:02, Paul Moore <[email protected]> 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. 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. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/JJAAVW2Y5F6V26V5YBMLHAD5B2BVMNEP/ Code of Conduct: http://python.org/psf/codeofconduct/
