Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder2.hal-mli.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <51015885.9060104@timgolden.me.uk>
References: <50FE5AC7.3050909@timgolden.me.uk> <kdm962$cc3$1@ger.gmane.org> <mailman.793.1358867242.2939.python-list@python.org> <50ff24e8$0$29994$c3e8da3$5496439d@news.astraweb.com> <mailman.851.1358902404.2939.python-list@python.org> <50ff5ffc$0$29877$c3e8da3$5496439d@news.astraweb.com> <mailman.879.1358935287.2939.python-list@python.org> <5100bd49$0$29877$c3e8da3$5496439d@news.astraweb.com> <CAHVvXxSHY5OztqH526b3DSuOvR6s8iA4ybh9pbj0pT4BDxQTCw@mail.gmail.com> <51011340.6020309@timgolden.me.uk> <CAHVvXxRFVn0BQy=4EsW30OJB+reVhO7teNyrRVdczVD+W_+R_A@mail.gmail.com> <51013B0C.6000309@timgolden.me.uk> <CAHVvXxSwbXD_C_zfn4nTj9XTFUzBJXRk+nzaE8xPW76t+M7cjw@mail.gmail.com> <51015885.9060104@timgolden.me.uk>
Date: Thu, 24 Jan 2013 16:08:50 +0000
Subject: Re: Retrieving the full command line
From: Oscar Benjamin <oscar.j.benjamin@gmail.com>
To: Tim Golden <mail@timgolden.me.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Python List <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.996.1359043732.2939.python-list@python.org>
Lines: 60
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:37606

On 24 January 2013 15:51, Tim Golden <mail@timgolden.me.uk> wrote:
> On 24/01/2013 15:28, Oscar Benjamin wrote:
>> On 24 January 2013 13:45, Tim Golden <mail@timgolden.me.uk> wrote:
>>> On 24/01/2013 11:30, Oscar Benjamin wrote:
>>>> I don't really understand what your spec is. Why do you need to
>>>> inspect this information from sys.argv? Can you not just always use
>>>> 'python -m pkg' as your entry point?
>>>
>> [SNIP]
>>>
>>> For completeness, I'm talking about the cherrypy Autoreloader which
>>> attempts to restart (via execv) whatever process was responsible for
>>> loading it in the first place, via an identical or equivalent command
>>> line. The current (cherrypy) code simply joins sys.executable and
>>> sys.argv but this fails in the face of python -m as we have seen.
>>>
>>> The cherrypy package has no especial knowledge of the structure of the
>>> application which imported it and so must piece together the command
>>> line somehow. Clearly, I can take various approaches of the sort
>>> which you've outlined, or subclass the reloader, or fetch the original
>>> command line from the OS, etc. It's not that this is a showstopper,
>>> merely slightly surprising. (To me).
>>
>> Ok I understand. Then I guess you want:
>>
>> import __main__
>> pkg = __main__.__package__
>
> Brilliant. Never thought of importing __main__. Thanks.
>
> For the benefit of anyone still watching, the code (which has to be
> compatible back to 2.3) looks something like this:
>
> <code>
> import __main__
>
> # [.. .snip ...]
>
> try:
>     is_package = bool(__main__.__package__)
> except NameError:
>     is_package = False
> if is_package:
>     args = [sys.executable, '-m', __main__.__package__] + sys.argv[1:]
> else:
>     args = [sys.executable] + sys.argv
>
> os.chdir(_startup_cwd) # avoids relative/absolute issues
> os.execv(args[0], args)
>
> </code>
>
> I don't pretend it's foolproot, but it certainly works for my particular
> case. Nor have I considered it against all the cases identified in PEP
> 432: http://www.python.org/dev/peps/pep-0432/#configuring-sys-argv

Does it work if you use the -m option to run a module rather than a script?


Oscar