Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to start *.py from PyCharm on Windows 10 #8

Open
ChrisPHL opened this issue Nov 14, 2019 · 1 comment
Open

Fail to start *.py from PyCharm on Windows 10 #8

ChrisPHL opened this issue Nov 14, 2019 · 1 comment

Comments

@ChrisPHL
Copy link

Hi Barney,

I'm happy to have found this Python module. Thank you so much! I included the functionality into my project and found sys.argv in windows.py evaluates to ['D:\path_to_my\script.py']. Since my script does not contain a shebang line nor the Windows system got a file association installed, the elevated call fails (of course) without any useful return value. :-/
Maybe there could be a test if the given file:

  • Has a file name extension that is registered with the system OR
  • Is a *.py an contains a shebang line with a windows executable

What do you think about that?

@barneygale
Copy link
Owner

Does the cwd_and_abs_paths branch help at all, out of interest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants