Jeff Edwards added the comment:
Interesting, I hadn’t realized that it would embed the FQ Executable path,
but that does make sense overall. I guess I had always planned on fixing
the ‘bin’ directory anyway afterwards, it’s just that the lack of relative
home made it significantly harder
Jeff Edwards added the comment:
I would say they’re not designed to be, but the also aren’t designed to not
be portable. This is often useful where open network access isn’t
reasonable, so access to Pip/pipx/pipenv is limited at best.
Suffice to say, is there a significant reason to not allow
New submission from Jeff Edwards :
Currently, the interpreter only supports absolute paths for the 'home'
directory in the pyvenv.cfg file. While this works when the interpreter is
always installed at a fixed location, it impacts the portability of virtual
environments and can make
Jeff Edwards added the comment:
It's interesting how long this issue has been around. It seems to be because
the form-urlencoded spec is specified as url-percent-encoding EXCEPT for ' ' -
'+', which does seem to be unintuitive.
To note, there are a few known cases where the exception does
