Open kyleredilla opened 2 years ago
Hi! Thanks for the issue. At first glance it appears that we're hitting the case where the env vars are set during conda activate
https://github.com/conda-forge/proj.4-feedstock/blob/master/recipe/scripts/activate.sh
Unfortunately, anaconda-project does not call conda activate
when running a command. See the end of PR #286
It seems like a good time to revisit the command run procedure.
Version info
anaconda-project
: 0.10.1conda
: 4.10.3I'm dealing with two variables which are set in the parent
conda
env which are not updated byanaconda-project run
that I've noticed so far, and I wonder if perhaps they should be? They arePROJ_LIB
, andGDAL_DATA
.This can cause issues with packages that depend on this happening, but setting them manually based on the
anaconda-project
env seems to fix the issues. Here is an example with PROJ, where thePROJ_LIB
var is not updated:Thanks! Loving the project so far! Happy to try contributing if this is indeed something to fix.