-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lockfiles debug #6141
Lockfiles debug #6141
Conversation
ResultsThe env dump in the py3.12 tests went like this, in part ...
Suspected RelevanceSo, I have a strong suspicion that the It does seem from the error messages that this key variable is not re-set to the correct path for the installed test environment, as it should have been. E.G. this message from the #6096 tests :
Trial to replicateI have now replicated this myself locally, by setting the path into an older conda env. E.G.
What it meansFrom further experiment, activating a conda env with proj/pyproj in it does always set PROJ_DATA, even in the latest versions. Certainly, if PROJ_DATA is set like as above, and then the new env is activated with "conda activate", then PROJ_DATA is changed by that as you would expect, and the above error does not occur :
|
⏱️ Performance Benchmark Report: f04064ePerformance shifts
Full benchmark results
Generated by GHA run |
Also tested : a "minimal" noxfile like this :
ResultsToo long+tedious to copy here, but it suffices to say that PROJ_DATA is not set in the environment where proj is installed. Checking the nox code, I believe that the So I conclude that However, consulting also our SSS modulefiles, which likewise include variables from activation scripts so as to mimic a "conda activate", it seems that PROJ_DATA is quite possibly the only one which is likely to cause trouble in this way. So in practice it's a marginal problem. In this specific case, another way to fix it could be to set |
Actually an attempt to dig a bit deeper into the #6096 #6135 problems