Running Python Code in Windows Batch File Trick
I found this really neat bit of .bat file magic that will let you save your python script code in a .bat file and run it in windows just like any other script. The nice thing about this is that you don’t have to create a separate “launch.bat” file with one “start python script.py” line in it.
This makes running python scripts in Windows more like it is on a Linux/Mac where you can easily add a #!/usr/bin/env python line to the script and run it directly.
Here’s the bit of tricky batch file magic that does it:
@setlocal enabledelayedexpansion && python -x "%~f0" %* & exit /b !ERRORLEVEL! #start python code here print "hello world"
The way it works is that the first line of the file does two different things.
- starts python interpreter passing the name of the file in, and the -x option will tell it to skip the first line (containing .bat file code)
- When python finishes the script exits.
This nifty trick makes it much nicer for writing admin scripts with python on Windows.
Update: fixed to properly pass command line arguments (%* argument passes through the command line arguments for the bat file to python)
More from halotis.com
- Finding inlink information from Yahoo! in Python
- RSS Twitter Bot in Python
- Translating Text Using Google Translate and Python
![Recommend [halotis]](http://s3.amazonaws.com/arkayne-media/img/logo-recommend-me.png){kind=logo}
Related posts:
- Automatically Respond to Twitter Messages
- Scrape Technorati Search Results in Python
- Scrape Advertisements from Google Search Results with Python
- Sending Email from Python using Gmail
- Python Web Crawler Script
Stumble it!
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:
Here’s what echo.bat looks like:
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable: c:> echo import sys; print ‘ ‘.join(sys.argv[1:]) >test.py c:> SET PATHEXT=%PATHEXT%;.py c:> test hello world hello world
This comment was originally posted on Reddit
Or alternatively … just register .py files as runnable? You’d have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it’s needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment varia