Fredrik Lundh fredrik at pythonware.com
Thu Mar 16 19:40:02 CET 2006

• Previous message: [Python-Dev] towards a stricter definition of sys.executable
• Next message: [Python-Dev] towards a stricter definition of sys.executable
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> > >     a) sys.executable points to the executable that was used to load the
> > >     Python interpreter library/dll.
> > >
> > >     this use is supported by the docstring and the implementation, and is quite
> > >     common in the wild.  an application using this interpretation may

Thomas:

> > py2exe used the a) interpretation. /.../
> > The use case for b) 'call sys.executable to run a Python script' makes
> > no sense for a py2exe'd application.

Trent:

> Ditto on both counts for PyXPCOM (Python embedded in Mozilla).

Looks like I might have to withdraw my (d) proposal, and, once again, suggest
that we stick to the "GetProgramFullPath" sense, as implemented, and add a
new variable for the originally intended but not really implemented "GetInter-
preterPath" sense...

Guido ?

</F>

---

• Previous message: [Python-Dev] towards a stricter definition of sys.executable
• Next message: [Python-Dev] towards a stricter definition of sys.executable
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list