Virtualenv detection may be too strict

[sbidoul]

From the FAQ: pip-deepfreeze erroneously complains python is not running in a virtualenv.

The most probable cause is that you used an older version of virtualenv which does not generate PEP 405 compliant virtual environments. virtualenv version 20 and later are supported, as well as the Python 3 native venv module. Should this problem be prevalent in practice, we may add support for older virtualenv versions, or add an option to ignore the virtualenv sanity check (which is only there to prevent pip-deepfreeze to corrupt the system Python packages by accident).

[wy6688]

I got this errors also in latest mamba/conda environment. any solution?

[sbidoul]

Ah, a pip-deepfreeze user using mamba/conda. That is interesting, welcome! :)

Concretely, I consider changing the virtual environment detection mechanism by checking if sys.prefix != sys.base_prefix.

I am not a conda user. Can you help me and verify that in a conda environment, and conversely if its not the case in the conda base environment (if that is a thing?).

[wy6688]

Sure, I will be happy to help. I attached the screenshot.

[wy6688]

you can use the miniconda or mamba to create a virtual environment.

[sbidoul]

Thanks. What I meant is, can you print(sys.prefix == sys.base_prefix) in a conda environment?

[wy6688]