Comments on: Running Python Code in Windows Batch File Trick

By: Youpsla

Youpsla — Sat, 03 Dec 2011 02:19:41 +0000

It’s not the same using the trick and addig.py in PATHEXT.

For example, I use pycron to launch a python script wich import modules.

Without the trick, I’ve an import module error at the first import.

I don’t know internallt how it works but it works !!

Thanks for the trick

By: Youpsla

Youpsla — Sat, 03 Dec 2011 02:19:19 +0000

It’s not the same using the trick and addig.py in PATHEXT.

For example, I use pycron to launch a python script wich import modules.

Without the trick, I’ve an import module error at the first import.

I don’t know internallt how it works but it works !!

Thanks for the trick

By: Youpsla

Youpsla — Sat, 03 Dec 2011 02:18:43 +0000

It’s not the same using the trick and addig.py in PATHEXT.

For example, I use pycron to launch a python script wich import modules.

Without the trick, I’ve an import module error at the first import.

I don’t know internallt how it works but it works !!

Thanks for the trick

By: Running Python Code in Windows Batch File Trick | Ben's Computer Graphics Blog

Mon, 15 Aug 2011 09:19:52 +0000

[...] Running Python Code in Windows Batch File Trick [...]

By: Matt Warren

Matt Warren — Tue, 25 Aug 2009 16:44:37 +0000

quite right. you can just set Windows to associate the .py file with python. what this .bat file trick accomplishes is to make it familiar to users that are not used to running .py files. Now they get a .bat file which they know they can click to run a program. It’s just one less thing that you have to explain to users of your scripts.

There are lots of people in my office that if I sent them a python script I would get a “What do I do with this?” type response. But they would know what to do with a .bat file.

By: Greg

Greg — Sun, 23 Aug 2009 04:37:11 +0000

Don’t get me wrong – much kudos to you for this cleverness. I just have zero use for this in a production environment.

By: Greg

Greg — Sun, 23 Aug 2009 04:32:42 +0000

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.

By: Brian

Brian — Sat, 22 Aug 2009 14:40:00 +0000

Why not just register .py files as runnable? You'd have to do this for every python file you want to launch, it prevents you from using the same file for both script and module, and it seems needlessly complex when you can accomplish the same goal for every python file simply by registering the .py extension (already done by the installer) and extending the PATHEXT environment variable:

c:\> echo import sys; print ' '.join(sys.argv[1:]) >test.py
c:\> SET PATHEXT=%PATHEXT%;.py
c:\> test hello world
hello world

By: Matt Warren

Matt Warren — Sat, 22 Aug 2009 13:55:11 +0000

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

Example Usage:

$ echo.bat test
test

Here’s what echo.bat looks like:

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

By: Jim

Jim — Sat, 22 Aug 2009 08:13:19 +0000

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