-
Notifications
You must be signed in to change notification settings - Fork 55
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
Can't run *.py scripts directly #36
Comments
It sounds like the 'bug' is fixed, or about to be fixed, by Appveyor. I think it would be good for the demo to directly execute a Python script, to show it works correctly, and it associates with the correct Python exe. Personally I dont like invoking python scripts that way, but it is a feature, and some people may want to do it. Ideally the demo script includes a Python script which has identical output to |
Reading more of the docs and playing with my hello world example, it looks like I should be setting |
Hmm. |
It's kinda sorta documented here, though all of the examples given are with 3 instead of 2: https://docs.python.org/3.3/using/windows.html#customizing-default-python-versions
You can see it in action by looking at these two builds: |
I don't think is worth making the demo more complex with registry-related dark magic. I prefer to stay simple and stick to using the python |
You run into this if you run
foo.py
instead ofpython foo.py
. The former is a no-op. http://help.appveyor.com/discussions/problems/2569-latest-appveyor-build-platform-update-introduced-a-python-problemIt looks like we can fix this by deleting a reg key, like this: buildinspace/peru@1290909
Should we add this fix to the demo? The demo doesn't directly execute any Python scripts, but maybe that would be a useful thing to add too?
The text was updated successfully, but these errors were encountered: