Running Python Code in Windows Batch File Trick – I found this really neat bit of .bat file magic that will let you.. http://bit.ly/4QopL

This comment was originally posted on Twitter

Sweet… now how do I stealth deploy the python interpreter to every PC in my office so that I never have to write another VBscript?

This comment was originally posted on Reddit

"Security" patch. :-)

This comment was originally posted on Reddit

lol windows. They have transparent glassy foggy graphics-accelerated window borders, but they still use the same tired conventions from the 90’s.

This comment was originally posted on Reddit

The irony is that (PowerShell)[http://en.wikipedia.org/wiki/Powershell] –Windows’ modern alternative to batch files– feels so Unix-y that I refuse to use it.

This comment was originally posted on Reddit

Nice trick. How would you recommend passing in invocation arguments from the command line? I’d like to be able to use sys.argv from within my .bat embedded python program.

thanks

I thought Windows environments had easy installation to client machines?

This comment was originally posted on Reddit

Running python in a windows .bat script: http://bit.ly/fd7Ns

This comment was originally posted on Twitter

Technically, yes. Politically, no.

This comment was originally posted on Reddit

How is this useful? On my machines, I simply associate .py extensions to Python. Done. Runs when I doubleclick it now. On others’ machines that don’t have Python, I compile my script using Py2Exe. Runs when they doubleclick it now.

This comment was originally posted on Reddit

I updated the batch file line to pass through the command line arguments.

Example Usage:

$ echo.bat test
test

Here’s what echo.bat looks like:

@setlocal enabledelayedexpansion && python -x "%~f0" %* & exit /b !ERRORLEVEL!
#start python code here
import sys
print sys.argv[1]

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit

Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world

This comment was originally posted on Reddit