launch .PY program Help

[Larz60+]

Hello,

You can always find out which version of python is running by typing

# For version 2.5 up to current version
python --version
# prior to 2.5 you will need:
python -c 'import sys; print(sys.version)'

from the command window (Start-->cmd)

The default version is determined by your system path,


from command window, type 'path'

You can find the python version in the string, should look similar to 'C:\Python34;', where 34 = version 3.4

Larz60+

[wavic]

If you just fire up python in the cmd (console) like:

C:\ > python

it will print the version before the interpreter prompt. At least in Linux that is what is happens. I think in Windows should be the same.

And there is no reason to copy/move the script in the directory where python.exe is located. You always can point to script with its full path.

[snippsat]

it will print the version before the interpreter prompt. At least in Linux that is what is happens. I think in Windows should be the same.

And there is no reason to copy/move the script in the directory where python.exe is located. You always can point to script with its full path.

It will work the same,but then need Environment Variables(Path) to be setup on Windows,
then python command will work from anywhere in cmd.

Python 3.5 has a box that can be check under installation,all earlier version has to a add to Path self.
So eg for Python 3.4 need to add ;C:\python34\;C:\python34\scripts to Path.

[Barrowman]

I don't use Windows but I think you could edit the file and put either:

#!c:\python34\python

or

#!c:\python27\python 

As the first line in the sna.py file and it should run by double clicking it or running it from the command line

[micseydel]

Windows doesn't use the Shebang.

[nilamo]

Windows doesn't use the Shebang.

That looks like it might not actually be true anymore: https://docs.python.org/3/using/windows....bang-lines
Or rather, new versions of the windows python launcher associate with files that don't have an extension, and maybe check to see if that file should be handled by python.

I think you'd still have to mark the file as executable, which is... not something I'd recommend.

[micseydel]

I don't see anything there suggesting a shebang is used on Windows. It just seems to say that since it's a comment, it's cross-compatible with Windows in the sense that Windows can ignore it.

[nilamo]

I just added "#! /usr/bin/python -v" to the top of a random python file, and ran it using "test.py" from the command line, not giving any indication (aside from file extension) that it was a python file. I also DID NOT mark the file executable.

And I saw a very large amount of verbose info that's normally never there.

So either windows is parsing shebangs, or python is :p

[metulburr]

I just added "#! /usr/bin/python -v" to the top of a random python file, and ran it using "test.py" from the command line, not giving any indication (aside from file extension) that it was a python file.  I also DID NOT mark the file executable.

And I saw a very large amount of verbose info that's normally never there.

So either windows is parsing shebangs, or python is :p

Do you have file extension .py associated with the python interpreter? Mine does this also but it is not because there is a shebang in the code...but because of file associations. A sure way to confirm this is to remove the file extension and rerun.

[micseydel]

Ah, I see now. Yes, it's the Python launcher doing it. Windows itself still doesn't do anything with the shebang. I did learn something new about Python's Windows launcher here though :)

It looks like it implies that if you specify a version as you would with Unix, that it'll work on Windows. Can anyone verify that? Also, I'd be a little surprised if the Windows path works on Windows, but even if it does, it seems a Unix shebang should be used for portability.