Is there a way to stop python from creating .pyc files, already in the shebang (or magic number if you will) of the Python script?
Not working:
#!/usr/bin/env python -B
-
2@VajkHermecz, no my question is much more specific.Prof. Falken– Prof. Falken2012-11-14 10:02:24 +00:00Commented Nov 14, 2012 at 10:02
-
Yeah, sorry related would have been a better term... srryVajk Hermecz– Vajk Hermecz2012-11-14 10:07:25 +00:00Commented Nov 14, 2012 at 10:07
-
2Voting to reopen because it has different implications than the duplicate.o11c– o11c2015-07-21 20:40:50 +00:00Commented Jul 21, 2015 at 20:40
-
The so called "duplicate" is a quite completely different question which does not have any answer related to shebang.user3224237– user32242372021-03-08 20:44:07 +00:00Commented Mar 8, 2021 at 20:44
Add a comment
|
4 Answers
it is possible by putting your python interperter path directly in the she bang instead of using env.
#!/usr/bin/python -B
of course this means you lose out on some of the portability benefits of using env. There is a discussion of this issue with env on the wikipedia Shebang page. They use python as one of their env examples.
Comments
According to the man page for env, you can pass name=value to set environment variables. The PYTHONDONTWRITEBYTECODE environment variable causes Python to not write .py[co] files (the same as the -B flag to python). So using
#!/usr/bin/env PYTHONDONTWRITEBYTECODE=1 python
should do the trick.
EDIT:
I tested this with a simple Python script:
#!/usr/bin/env PYTHONDONTWRITEBYTECODE=1 python
print 1
then
$chmod +x test.py
$./test.py
1
$ls
test.py
(but not test.pyc)
4 Comments
Prof. Falken
For me the script just hangs...
asmeurer
Does it work with just
python -B script.py? I just tested a simple script, and it seemed to work OK to me.
Marwan Alsabbagh
me too. this doesn't seem to work.
Prof. Falken
Yes, it works with
python -B script.py Yes, if and only if, we assume the Python program runs in a somewhat POSIX compatible system (for /bin/sh), this will work:
(IMPROVED based on input from glglgl)
#!/bin/sh
"exec" "python" "-B" "$0" "$@"
# The rest of the Python program follows below:
8 Comments
Prof. Falken
Note to self: later improve with stackoverflow.com/a/9057699/193892
glglgl
Looks great! The
"s are for the shell and ignored by python...glglgl
But it breaks syntax highlighting...
Prof. Falken
@glglgl, haha, I though it might. Will it appear again if the script is called something.py ? :)
glglgl
Yes, that would do it. But then the script has a .py extension... not nice either, but probably you'll have to die one death...
|
Alas, no. The shebang stuff is limited to giving an executable and one parameter.
So env tries to execute python -B with the given file as one argument instead of python with -B and the current file as two arguments.
I don't see a way to achieve the wanted goal.
1 Comment
lqc
The funny part is that Python Windows Launcher doesn't know about this limitation and passes the options (un)correctly. So for once Python on Window works better ;)