Question

:

and

sys.argv[0]

因为两者似乎都是一样的:它们持有文字名称。

If there is no difference, then why is it that is used in almost all someplaces whereas I have never seen sys.argv[0] being used.

Answer 1

。 www.un.org/Depts/DGACM/index_french.htm

Answer 2

如果你在你的餐厅的“主要”文字中,这只是这样。如果你进口其他档案,__file__将载有查阅该档案的途径,但sys.argv仍持有同样的价值。

Answer 3

It s like Sven said.

MiLu@Dago: /tmp > cat file.py
import sys
import blub
print __file__
print sys.argv[0]

MiLu@Dago: /tmp > cat blub.py
import sys
print "BLUB: " + __file__
print "BLUB: " + sys.argv[0]

MiLu@Dago: /tmp > python file.py
BLUB: /tmp/blub.pyc
BLUB: file.py
file.py
file.py

I thought that __file__ was replaced with the filename during a preprocessor step. I was not 100 % sure that s actually the case in Python - but it is in C/C++ and Perl. In Python, this might be different as the __file__ is also correct for compiled Python files (pyc), and there doesn t seem to be any trace of the filename in that file s contents.

Answer 4

Actually argv[0] might be a script name or a full path to the script + script name, depending on the os.

Here s the entry in official documentation http://docs.python.org/py3k/library/sys.html#sys.argv

Answer 5

You can detect whether your *.py code is running as a module or as the main script!

http://www.ohchr.org。

It s useful because you can have code, like a main block, tests, etc. in a file that only runs if it s NOT being used in a module aka it s the main script

if __file__.endswith(sys.argv[0]):
    #you re the main script

友情链接