Antoine Pitrou pitrou.net> writes:
> If that's the only failing test, we can simply skip it when run from a
> venv. A non-existent argv[0] is arguably a borderline case which you
> should only encounter when e.g. embedding Python.
Actually there are four module failures: test_sys, test_packaging
On Fri, 4 May 2012 08:44:25 + (UTC)
Vinay Sajip wrote:
> IIUC, the program name of the Python executable is set to whatever argv[0] is.
> Is there a reason for this, rather than using one of the various OS-specific
> APIs [1] for getting the name of the running executable? The reason I ask is
On Fri, 4 May 2012 13:29:14 +0100
Michael Foord wrote:
>
> On 4 May 2012, at 09:44, Vinay Sajip wrote:
>
> > IIUC, the program name of the Python executable is set to whatever argv[0]
> > is.
> > Is there a reason for this, rather than using one of the various OS-specific
> > APIs [1] for getti
On 4 May 2012, at 09:44, Vinay Sajip wrote:
> IIUC, the program name of the Python executable is set to whatever argv[0] is.
> Is there a reason for this, rather than using one of the various OS-specific
> APIs [1] for getting the name of the running executable? The reason I ask is
> that in a vi
IIUC, the program name of the Python executable is set to whatever argv[0] is.
Is there a reason for this, rather than using one of the various OS-specific
APIs [1] for getting the name of the running executable? The reason I ask is
that in a virtual environment (venv), the exe's path is the only t
