This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mikekaganski
Recipients mikekaganski, paul.moore, steve.dower, tim.golden, zach.ware
Date 2022-02-14.18:42:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644864121.29.0.790596029405.issue46751@roundup.psfhosted.org>
In-reply-to
Content
Using cyqwin 3.3.4-2, and python3:

Python 3.9.10 (main, Jan 20 2022, 21:37:52)
[GCC 11.2.0] on cygwin

Trying this bash command line:

> python3 C:/path/to/script.py

results in this error:

"python3: can't open file '/cygdrive/c/path/to/curdir/C:/path/to/script.py': [Errno 2] No such file or directory"

OTOH, calling it like

> python3 /cygdrive/c/path/to/script.py

gives the expected output:

"usage: script.py [-h] ..."

It seems that python3 doesn't recognize "C:/path/to/script.py" to be a proper full path under cygwin, while most other cygwin apps handle those fine. E.g.,

> nano C:/path/to/script.py

opens the script for editing without problems.

The mentioned path syntax is useful and supported under cygwin, so it would be nice if python3 could support it, too. Especially useful it is in mixed development environment, mixing Windows native tools and cygwin ones; using such path style allows to use same paths for both kinds of tools, simplifying scripts.
History
Date User Action Args
2022-02-14 18:42:01mikekaganskisetrecipients: + mikekaganski, paul.moore, tim.golden, zach.ware, steve.dower
2022-02-14 18:42:01mikekaganskisetmessageid: <1644864121.29.0.790596029405.issue46751@roundup.psfhosted.org>
2022-02-14 18:42:01mikekaganskilinkissue46751 messages
2022-02-14 18:42:01mikekaganskicreate