running python hello world

[Avarage_Joe]

Hi,

installed python 3.6.5 x64 to a windows 10 x64 machine.

- installed for all users
- changed install path to c:\python36
- created a test file called hello.py with the canonical:

print("Hello World!")

- when i try run it from command line with "python hello.py" it works fine.

when i try "py hello.py" or just "hello.py" i get an empty line..



- tried run as admin the command line



Thanks,
Joe

[Larz60+]

when i try run it from command line with "python hello.py" it works fine

That is the correct way to run it.

py hello.py

won't work unless you created a symbolic link to python
hello.py is a text file, and can't execute without an interpreter.
Remember that python is an interpreted language, and cannot run alone.

[Avarage_Joe]

hello.py is a text file, and can't execute without an interpreter.

Quote:
py hello.py
won't work unless you created a symbolic link to python
hello.py is a text file, and can't execute without an interpreter.
Remember that python is an interpreted language, and cannot run alone.

I Found a way..
on an elevated command line 2 commands

C:\> assoc .py=Python
C:\> ftype Python="C:\python36\python.exe" %1 %*

Regards,
Joe

[Larz60+]

C:\> assoc .py=Python

which is a symbolic link!

[Avarage_Joe]

Hi larz60+,

Remember that python is an interpreted language, and cannot run alone.

Installed Python for that.

py hello.py - won't work unless you created a symbolic link to python

Tried that with aliasing: "doskey py=python.exe" and with full path "doskey py=c:\python36\python.exe"
Solved it with: "doskey py=c:\python36\python.exe $*"

hello.py is a text file, and can't execute without an interpreter.

I agree! it is like notepad interprets .txt file and I don't need to write anything else at the command line to open text.txt. (e.g "notepad text.txt")

1. C:\> assoc .py=Python
2. C:\> ftype Python="C:\python36\python.exe" %1 %*

those commands are doing:
1. defining a new filetype by extension and giving it a name.- not a location reference relative or hard. so i guess it just key value pair list stored for later use.
2. associating that new filetype with the right open tool. - which is more of a function that we don't know implementing symlinks or just a var.

I can now run python files like exe files by directly typing (autocomplete) their name and its great :D

I appreciate your response. (it got me on the right way to solve it.)
Thanks,
Joe

[sparkz_alot]

*It would have been easier to just ensure your environmental variables were set correctly.

Output:
C:\>cd python

C:\Python>test.py
hello from Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 bit (AMD64)]

C:\Python>py test.py
hello from Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 bit (AMD64)]

C:\Python>

[snippsat]

Follow this to make sure your environmental variables is set correct.
Python 3.6 and pip installation under Windows | Part-2

[Avarage_Joe]

Hi Sparkz,

*It would have been easier to just ensure your environmental variables were set correctly.

since "python test.py" worked from anywhere at the system I assumed environment variables are ok.

I've restarted the machine & checked the basics according to this here: https://docs.python.org/3/using/windows.html

1. long path is enabled - set the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem@LongPathsEnabled to 1.
2. check python path as a system environment variable - C:\>set PATH=C:\Python36;%PATH%

solved by creating file association

Regards,
Joe

[Avarage_Joe]

Hi snippsat,

Thanks for the virtual environment tutorial!
It will help me to better separate and manage multiple projects without dependencies issues.

Regards,
Joe