Greetings,
It may be good to list out your environment and see which packages are coming
from conda and which are coming from pip/pypi
conda list
daryl
________________________________________
From: Weber, Jim <Jim.Weber@xxxxxxx>
Sent: Wednesday, May 18, 2022 2:38 PM
To: Herzmann, Daryl E [AGRON]; python-users@xxxxxxxxxxxxxxxx
Subject: RE: miniconda error message
Daryl,
Miniconda is installed and started in the .bashrc so all path variables are
set then. It seems to be tied to when I did the metpy update, it installed many
other updates at that time also. One of them seems to have caused a small issue
to get things out of sync. Admittedly, I am not very proficent in the conda
enviroment as this is still new to me.
I did realize there was one more part of the line that I did not include in my
original email. The entire error message is below when I run a python script.
Specifically I am using a reciepe created by Brian Blaylock called
mapping_GOES16_TrueColor.py where I have modified it for my local use.
/home/ldm/miniconda3/lib/python3.9/site-packages/pyproj/__init__.py:89:
UserWarning: pyproj unable to set database path.
_pyproj_global_context_initialize()
It seems to be tied to the import metpy in the beginning as that specific error
goes away if I comment it out (of course other parts do not work).
When I do a printenv, I do see "PROJ_LIB=/home/ldm/miniconda3/share/proj"
listed so the variable is set.
Looking back through my notes of when I originally installed everything I see
that I had reached out regarding an error message with pandas. A user gave me a
quick fixed of typing "pip uninstall pandas" followed by "pip install -U
pandas" but then warned me about a mixed pip-conda environment getting out of
sync. Could this be what is going on that I did a metpy update but something
got out of sync because one other part was installed with pip? Not to get too
far off topic, my notes suggest my first command during the installed was "pip
install metpy" followed by "conda install -c conda-forge metpy"
I guess I am also asking is my install correct or am I on a wrong tangent with
my install that future updates will cause me headache.
Sorry for the confusion and rambling, this is still a learning process for me.
Jim
-----Original Message-----
From: Herzmann, Daryl E [AGRON] <akrherz@xxxxxxxxxxx>
Sent: Tuesday, May 17, 2022 11:46 PM
To: Weber, Jim <Jim.Weber@xxxxxxx>; python-users@xxxxxxxxxxxxxxxx
Subject: Re: miniconda error message
Greetings,
How are you instantiating miniconda? If you are just manually setting a $PATH
variable, then your shell is missing out on other variables that miniconda may
be wishing to set at activation time. In this case PROJ_LIB. see:
etc/conda/activate.d/proj4-activate.sh
Additionally, a best practice is to install packages into a dedicated
environment and not the base environment.
Now for LDM, having each shell invocation run a conda environment activation
can create horrible latency for some workflows. In such case, just add the
needed PROJ_LIB setting when you set your PATH. For your example I am setting
export PROJ_LIB=/home/ldm/miniconda3/share/proj
daryl
________________________________________
From: python-users <python-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Weber,
Jim <Jim.Weber@xxxxxxx>
Sent: Tuesday, May 17, 2022 2:15 PM
To: python-users@xxxxxxxxxxxxxxxx
Subject: [python-users] miniconda error message
Hi,
I upgraded to metpy 1.3.0 last month and notice a little after I was getting a
warning message. It does not seem to affect the end result of anything that I
run, but it throws it out for anything that I run. Any idea of how I can
resolve the issue for this error:
/home/ldm/miniconda3/lib/python3.9/site-packages/pyproj/https://urldefense.proofpoint.com/v2/url?u=http-3A__-5F-5Finit-5F-5F.py&d=DwIFAg&c=uw6TLu4hwhHdiGJOgwcWD4AjKQx6zvFcGEsbfiY9-EI&r=KKIRMcmZ6BcKOjHM4171gGDDLEx31ZuiUy6Gn81J_cs&m=BMlerE2UKcRw0Su-YOnb-GIQ3I318UBjkUf-J0Z77Y2bWkl_YC86KWmjfx_kpi2W&s=kSytVwiagj1W9KzuBn7HlnxnOmKIOwean1FjmjUTwIw&e=
:89: UserWarning: pyproj unable to set database path.
Thanks for any help!
Jim Weber
This message and its attachments may contain legally privileged or confidential
information. It is intended solely for the named addressee(s). If you are not
an addressee indicated in this message (or responsible for delivery of the
message to an addressee), you may not copy or deliver this message or its
attachments to anyone. Rather, you should permanently delete this message and
its attachments and kindly notify the sender by reply e-mail. Any content of
this message and its attachments that does not relate to the official business
of Fox Corporation, or its subsidiaries must be taken not to have been sent or
endorsed by any of them. No representation is made that this email or its
attachments are without defect.
This message and its attachments may contain legally privileged or confidential
information. It is intended solely for the named addressee(s). If you are not
an addressee indicated in this message (or responsible for delivery of the
message to an addressee), you may not copy or deliver this message or its
attachments to anyone. Rather, you should permanently delete this message and
its attachments and kindly notify the sender by reply e-mail. Any content of
this message and its attachments that does not relate to the official business
of Fox Corporation, or its subsidiaries must be taken not to have been sent or
endorsed by any of them. No representation is made that this email or its
attachments are without defect.
