blocks|key|1194023|text|最好使用环境变量来实现这一点。请参阅python文档：http://docs.python.org/2/using/cmdline.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1194024|对于您的案例：|1194025|export+PYTHONUNBUFFERED=1
script.py|code-block|syntax|javascript|1194026|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.python.org/2/using/cmdline.html^0|R|17|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

It is better to use environment variable to enable this. See python doc : <a href="http://docs.python.org/2/using/cmdline.html">http://docs.python.org/2/using/cmdline.html</a>

for your case:

<pre><code>export PYTHONUNBUFFERED=1
script.py
</code></pre>

blocks|key|979588|text|在某些环境中，env不会拆分参数。所以你的环境在你的路径中寻找python+-u。我们可以使用sh来解决这个问题。用下面的代码行替换您的shebang，一切都会好起来的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|979589|#!/bin/sh
''''exec+python+-u+--+"$0"+${1%2B"$@"}+#+'''
#+vi:+syntax=python|code-block|syntax|javascript|979590|附注：我们不需要担心到sh的路径，对吗？|979591|entityMap^0|V|9|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

In some environment, env doesn't split arguments.
So your env is looking for <code>python -u</code> in your path.
We can use sh to work around.
Replace your shebang with the following code lines and everything will be fine.

<pre><code>#!/bin/sh
''''exec python -u -- "$0" ${1+"$@"} # '''
# vi: syntax=python
</code></pre>

p.s. we need not worry about the path to sh, right?

blocks|key|979658|text|这可能有点过时了，但是env(1)手册告诉我们可以在这种情况下使用'-S‘|type|unstyled|depth|inlineStyleRanges|entityRanges|data|979659|#!/usr/bin/env+-S+python+-u|code-block|syntax|javascript|979660|它在FreeBSD上似乎运行得很好。|979661|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This might be a little bit outdated but env(1) manual tells one can use '-S' for that case

<pre><code>#!/usr/bin/env -S python -u
</code></pre>

It seems to work pretty good on FreeBSD.

blocks|key|1193939|text|在Linux上使用shebang时，解释器名称后面的整个行将被解释为单个参数。python+-u被传递给env，就像您输入了：/usr/bin/env+'python+-u'一样。/usr/bin/env会搜索一个名为python+-u的二进制文件，但实际上并没有这个文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1193940|entityMap^0|13|9|1G|3|1R|O|2I|C|31|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

When you use shebang on Linux, the entire rest of the line after the interpreter name is interpreted as a single argument. The <code>python -u</code> gets passed to <code>env</code> as if you'd typed: <code>/usr/bin/env 'python -u'</code>. The <code>/usr/bin/env</code> searches for a binary called <code>python -u</code>, which there isn't one.

blocks|key|1193906|text|向shebang行传递参数不是标准的，并且在Linux中不能与env结合使用。bash的解决方案是使用内置命令"+set“来设置所需的选项。我认为您可以使用python命令来设置stdin的无缓冲输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1193907|my2c|1193908|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Passing arguments to the shebang line is not standard and in as you have experimented do not work in combination with env in Linux. The solution with bash is to use the builtin command "set" to set the required options. I think you can do the same to set unbuffered output of stdin with a python command.

my2c

blocks|key|979707|text|这是一个替代/usr/bin/env的脚本，它允许在散列上传递参数，基于/bin/bash，并且限制了在可执行文件路径中不允许使用空格。我称之为"envns“(env无空格)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|979708|#!/bin/bash

ARGS=(+$1+)++#+separate+$1+into+multiple+space-delimited+arguments.
shift+#+consume+$1

PROG=`which+${ARGS[0]}`
unset+ARGS[0]+#+discard+executable+name

ARGS%2B=(+"$@"+)+#+remainder+of+arguments+preserved+"as-is".
exec+$PROG+"${ARGS[@]}"|code-block|syntax|javascript|979709|假设此脚本位于/usr/local/bin/envns，下面是您的shebang行：|979710|#!/usr/local/bin/envns+python+-u|979711|在Ubuntu13.10和cygwin+x64上测试。|979712|entityMap^0|6|C|10|9|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

Here is a script alternative to <code>/usr/bin/env</code>, that permits passing of arguments on the hash-bang line, based on <code>/bin/bash</code> and with the restriction that spaces are disallowed in the executable path. I call it "envns" (env No Spaces):

<pre><code>#!/bin/bash

ARGS=( $1 ) # separate $1 into multiple space-delimited arguments.
shift # consume $1

PROG=`which ${ARGS[0]}`
unset ARGS[0] # discard executable name

ARGS+=( "$@" ) # remainder of arguments preserved "as-is".
exec $PROG "${ARGS[@]}"
</code></pre>

Assuming this script is located at /usr/local/bin/envns, here's your shebang line:

<pre><code>#!/usr/local/bin/envns python -u
</code></pre>

Tested on Ubuntu 13.10 and cygwin x64.

blocks|key|979534|text|这是一个杂乱无章的东西，需要bash，但它是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|979535|#!/bin/bash

python+-u+<(cat+<<"EOF"
#+Your+script+here
print+"Hello+world"
EOF
)|code-block|syntax|javascript|979536|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is a kludge and requires bash, but it works:

<pre><code>#!/bin/bash

python -u &lt;(cat &lt;&lt;"EOF"
# Your script here
print "Hello world"
EOF
)
</code></pre>

blocks|key|979763|text|基于Larry+Cai的回答，env允许您直接在命令行中设置变量。这意味着-u可以在python之前被等效的PYTHONUNBUFFERED设置替换|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|979764|#!/usr/bin/env+PYTHONUNBUFFERED="YESSSSS"+python|code-block|syntax|javascript|979765|适用于RHEL+6.5。我非常确定env的这个特性是通用的。|979766|entityMap^0|F|3|11|2|16|6|1I|G|0|0|H|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

Building off of Larry Cai's answer, <code>env</code> allows you to set a variable directly in the command line. That means that <code>-u</code> can be replaced by the equivalent <code>PYTHONUNBUFFERED</code> setting before <code>python</code>:

<pre><code>#!/usr/bin/env PYTHONUNBUFFERED="YESSSSS" python
</code></pre>

Works on RHEL 6.5. I am pretty sure that feature of <code>env</code> is just about universal.

blocks|key|979853|text|我最近为env的GNU+Coreutils版本写了一个补丁来解决这个问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|979854|http://lists.gnu.org/archive/html/coreutils/2017-05/msg00018.html|979855|如果你有这样的能力，你可以这样做：|979856|#!/usr/bin/env+:lang:--foo:bar|code-block|syntax|javascript|979857|env会将:lang:foo:--bar拆分为lang、foo和--bar字段。它将在PATH中搜索解释器lang，然后使用参数--foo、bar以及脚本的路径和脚本的参数来调用它。|979858|还有一个在选项中间传递脚本名称的功能。假设您想要运行lang+-f+<thecriptname>+other-arg，后跟其余的参数。使用这个打了补丁的env，它是这样完成的：|979859|#!/usr/bin/env+:lang:-f:{}:other-arg|979860|最左边的等同于{}的字段被替换为后面的第一个参数，在hash+bang调用下，这个参数是脚本名。然后删除该参数。|979861|在这里，other-arg可以是由lang处理的内容，也可以是由脚本处理的内容。|979862|要更好地理解，请参阅补丁中的大量echo测试用例。|979863|我选择:字符是因为它是POSIX系统上的PATH中使用的现有分隔符。由于env执行PATH搜索，因此它不太可能用于名称包含冒号的程序。{}标记来自find实用程序，该实用程序使用它来表示在-exec命令行中插入路径。|979864|entityMap|0|LINK|mutability|MUTABLE|url^0|4|3|0|0|1T|0|0|0|0|0|3|5|F|N|4|S|3|W|5|17|4|1H|4|1S|5|1Y|3|0|Q|W|24|3|0|0|7|2|0|4|9|H|4|0|G|4|0|3|1|K|4|10|3|15|4|1V|2|21|4|2M|5|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|H|3|I|5|6|7|1G|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1H|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|C]]|D|@]|E|$]]|$1|S|3|T|5|L|7|26|8|@]|D|@]|E|$M|N]]|$1|U|3|V|5|6|7|27|8|@$9|28|A|29|B|C]]|D|@]|E|$]]|$1|W|3|X|5|6|7|2A|8|@$9|2B|A|2C|B|C]|$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2F|8|@$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|10|3|11|5|6|7|2I|8|@$9|2J|A|2K|B|C]|$9|2L|A|2M|B|C]|$9|2N|A|2O|B|C]|$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]|$9|2V|A|2W|B|C]]|D|@]|E|$]]|$1|12|3|-4|5|6|7|2X|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|G]]]]

I recently wrote a patch for the GNU Coreutils version of <code>env</code> to address this issue:

<a href="http://lists.gnu.org/archive/html/coreutils/2017-05/msg00018.html" rel="nofollow noreferrer">http://lists.gnu.org/archive/html/coreutils/2017-05/msg00018.html</a>

If you have this, you can do:

<pre><code>#!/usr/bin/env :lang:--foo:bar
</code></pre>

<code>env</code> will split <code>:lang:foo:--bar</code> into the fields <code>lang</code>, <code>foo</code> and <code>--bar</code>. It will search <code>PATH</code> for the interpreter <code>lang</code>, and then invoke it with arguments <code>--foo</code>, <code>bar</code>, plus the path to the script and that script's arguments.

There is also a feature to pass the name of the script in the middle of the options. Suppose you want to run <code>lang -f &lt;thecriptname&gt; other-arg</code>, followed by the remaining arguments. With this patched <code>env</code>, it is done like this:

<pre><code>#!/usr/bin/env :lang:-f:{}:other-arg
</code></pre>

The leftmost field which is equivalent to <code>{}</code> is replaced with the first argument that follows, which, under hash bang invocation, is the script name. That argument is then removed.

Here, <code>other-arg</code> could be something processed by <code>lang</code> or perhaps something processed by the script.

To understand better, see the numerous <code>echo</code> test cases in the patch.

I chose the <code>:</code> character because it is an existing separator used in <code>PATH</code> on POSIX systems. Since <code>env</code> does <code>PATH</code> searching, it's vanishingly unlikely to be used for a program whose name contains a colon. The <code>{}</code> marker comes from the <code>find</code> utility, which uses it to denote the insertion of a path into the <code>-exec</code> command line.

I needed to have a directly executable python script, so i started the file with <code>#!/usr/bin/env python</code>. However, I also need unbuffered output, so i tried <code>#!/usr/bin/env python -u</code>, but that fails with <code>python -u: no such file or directory</code>.

I found out that <code>#/usr/bin/python -u</code> works, but I need it to get the <code>python</code> in <code>PATH</code> to support virtual <code>env</code> environments.

What are my options?

Cannot pass an argument to python with "#!/usr/bin/env python"

解释器

FreeBSD

Linux

我需要一个直接可执行的python脚本，所以我用#!/usr/bin/env python启动了这个文件。但是，我还需要无缓冲的输出，所以我尝试了#!/usr/bin/env python -u，但使用python -u: no such file or directory失败了。我发现#/usr/bin/python -u可以工作，但我需要它来让PATH中的python支持虚拟env环境。我有什

问无法使用"#!/usr/bin/env python“将参数传递给python
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使用"#!/usr/bin/env python“将参数传递给pythonEN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使用"#!/usr/bin/env python“将参数传递给python
EN