Open beenje opened 8 months ago
IIRC, it was required to load the dependency on GMP correctly (from the conda ecosystem) rather than the system-wide installed one.
CONDA_PREFIX is set if you activate a conda environment. You might have a valid use case for not doing so.
I wrote the patch three years ago. Python has improved a lot since then. Perhaps the patch is not required anymore or it needs to be fixed to not always assume that that env variable is always available.
CONDA_PREFIX is set if you activate a conda environment. You might have a valid use case for not doing so.
Activating a conda environment is not necessary, so in most cases we in fact don't activate the environment, but call the binaries of this environment directly. For example, calling path/to/conda/env/bin/python
works as well as activating the environment and then calling python
.
Trying to use this package without activating the conda env (but using the full python path) raises:
I see there is patch to rely on
CONDA_PREFIX
: https://github.com/conda-forge/pycryptodomex-feedstock/blob/96cc661b787d106b82c42aeb3719a25259997a2b/recipe/0001-Make-load_lib-CONDA_PREFIX-aware.patch#L26Is this really still required? I don't see any such patch in https://github.com/conda-forge/pycryptodome-feedstock
I think it's better if we don't have to rely on this CONDA variable.