layday
layday
Apple's `sysonfig._get_default_scheme` does accurately reflect `sys.prefix`. The issue here is that the `sys.prefix` of the running interpreter (i.e. the platform scheme) is different from the virtual environment's. Apple falls foul...
> You probably meant `sys.base_prefix`; because `sys.prefix` points to the virtual environment’s root when the interpreter is inside one. `sysconfig._get_default_scheme` returns the correct scheme provided that it is called from...
> Assuming that’s correct That is correct. > So pipx might not have much choice but to fix the logic to fetch the information from the virtual environment instead. I...
Right, PyPy3 uses a scheme for venvs which diverges from `posix_prefix`, so we must necessarily rely on `sysconfig`. I find starting up a subprocess just to find what scheme's being...
Transferred to the build tracker for greater visibility.
This could have one of a number of causes: * the `purelib` path is incorrect * `importlib_metadata` is not able to find any meta path finders which implement `find_distributions` *...
Should ensurepip not error then if it can't install pip if pip is not installed system-wide? I was under the impression that it did on Debian.
Are you manipulating the PYTHONPATH in Spack?
I assume what's happening is pip does not install itself in the venv because it believes it's already installed. When you pass `--with-ensurepip=upgrade`, the version from ensurepip is higher than...
So in the environment that you execute build there's no pip? Are you sure?