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?
Sorry about the confusion. I think my original point was simply one of surprise that sys.argv wouldn't essentially mirror the elements of the command line which I used to get there. The specifics of my use-case weren't really too important. 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). TJG -- http://mail.python.org/mailman/listinfo/python-list
