How a script can know if it has been called with the -i command line option?

[Michele Simionato]

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?
TIA,

Michele Simionato

[Thomas Heller]

Michele Simionato schrieb:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?
TIA,

Michele Simionato

I don't know how to get the command line flags, but the variable you are interested
in is this one:

from ctypes import *
print c_int.in_dll(py thonapi, "Py_Interactive Flag")

;-)

Thomas

[commander.coder]

Michele Simionato wrote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

In the optparse module.

Jim

[Carsten Haese]

On Thu, 2006-12-21 at 11:22 -0800, co************* @hotmail.com wrote:

Michele Simionato wrote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

In the optparse module.

That doesn't answer the question. The OP wants to inspect the options
passed to the interpreter, not the options passed to the script.
optparse aids in parsing sys.argv, which only contains the options that
are passed to the script.

-Carsten

[Hendrik van Rooyen]

"Michele Simionato" <mi************ ***@gmail.comwr ote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

sys.argv() ?

- Hendrik

[Michele Simionato]

Hendrik van Rooyen wrote:

"Michele Simionato" <mi************ ***@gmail.comwr ote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

sys.argv() ?

- Hendrik

No, read what Carsten said:
"""
That doesn't answer the question. The OP wants to inspect the options
passed to the interpreter, not the options passed to the script.
optparse aids in parsing sys.argv, which only contains the options that
are passed to the script.
"""

[Peter Wang]

Michele Simionato wrote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

I realize this is quite a hack, but the entire command line is
preserved in the process's entry in the OS's process table. if you do
"ps -ax" you will see that the interpreter was invoked with -i. I
didn't test this under windows, but it works on Mac and Linux.

[Michael B. Trausch]

Peter Wang wrote:

Michele Simionato wrote:

>The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py. I looked
at the sys module
but I don't see a way to retrieve the command line flags, where should
I look?

I realize this is quite a hack, but the entire command line is
preserved in the process's entry in the OS's process table. if you do
"ps -ax" you will see that the interpreter was invoked with -i. I
didn't test this under windows, but it works on Mac and Linux.

There is a set of utilities that have UNIX-like ps behavior, but, as is
typical for Windows, they don't work the way their UNIX and UNIX-like
counterparts do. Does 'ps' work from within Cygwin, and if so, would
redistributing that be an option?

-- Mike

[Tim Golden]

Michele Simionato wrote:

The subject says it all, I would like a script to act differently when
called as
$ python script.py and when called as $ python -i script.py.

[Michael B. Trausch]

There is a set of utilities that have UNIX-like ps behavior, but, as is
typical for Windows, they don't work the way their UNIX and UNIX-like
counterparts do. Does 'ps' work from within Cygwin, and if so, would
redistributing that be an option?

If you wanted to get the command line from within
Windows, you could use win32api.GetCom mandLine.
I think the OP's on Linux, and in any case you'd have
to do your own parsing, but...

<dump>
c:\>python -i
Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]
on win32
Type "help", "copyright" , "credits" or "license" for more information.

>>import win32api
win32api.GetC ommandLine ()

'python -i'

>>>

</dump>

TJG

[Hendrik van Rooyen]

"Michele Simionato" <mi************ ***@gmail.comwr ote:

Hendrik van Rooyen wrote:

"Michele Simionato" <mi************ ***@gmail.comwr ote:

but I don't see a way to retrieve the command line flags, where should
I look?

sys.argv() ?

- Hendrik

No, read what Carsten said:
"""
That doesn't answer the question. The OP wants to inspect the options
passed to the interpreter, not the options passed to the script.
optparse aids in parsing sys.argv, which only contains the options that
are passed to the script.
"""

True. - I was under the impression that sys.argv has all the stuff in it,
but it just ain't so - I made a file called junk.py containing two lines:

import sys
print sys.argv

and sys.argv just has junk.py in it, for both styles of command line.

I also noticed that if you do the following:

python junk.py -i

then the interpreter is not interactive. I was also not aware that
the options had positional dependency.

you could do a work around by calling it like this:

python -i junk.py -i

then sys.argv has the extra -i...

or better, insist on being told in both cases with say -i and -n at the end.

it does not answer the real question, though, as someone could lie to you.

- Hendrik