Re: [python-users] miniconda error message

  • To: "Weber, Jim" <Jim.Weber@xxxxxxx>, "python-users@xxxxxxxxxxxxxxxx" <python-users@xxxxxxxxxxxxxxxx>
  • Subject: Re: [python-users] miniconda error message
  • From: "Herzmann, Daryl E [AGRON]" <akrherz@xxxxxxxxxxx>
  • Date: Wed, 18 May 2022 20:11:14 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=iastate.edu; dmarc=pass action=none header.from=iastate.edu; dkim=pass header.d=iastate.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Lczqn1RMUdYJPuM9giSY9iFMPzT0VJs2dOodcXBjs3o=; b=mg5x3z+sOUlz1m4q73pPsWiBZ9ihYGSHOcM5kklEsepj+lOM8aRMSq2ct9gpfF0XkaUMWlKExJNycWs8SYVPejDqcNmXiiTsbyctBNfKmdnm8A567Swyrsl4lN8stuDn5f0ZEXfLwhGghpwddJS2QItlmqxXdVqWi0Gf3J3JwQyV6eSq+TWKWa8KIv1pMbtZU/t339WFqfrx5xYDhjwrzXgisEUmwLZV78zKRiarEXmJSeHBtKDWqUUmWNuK1pyqswNrtjY9636beyRMyV8r/hE7VuJlzC5KRXqainkZQ8ssiXjk036ob8/2P7iZiSFoCyvb+YKNFRjY24k2j5WT8A==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i7oVOoDAfa4mApIQi4Obpk3+DbWtDjS7aiG/mkCdPTW0nEkPXmtMPCnR3/NkkP35F5oPpK9bw4fB1k9P5U46cUtHKCOzN8PA5yRkHjtuCRTEFwBpBkJkH9zogpjH9wfSbuCvgon9Yo8+7eYKbzH7+/OIZ3A/5DSVsjATdXYMaffAad7nMgirzfcewI1m/3lYrr48aZD8AMgdEyrgHTsC3Te4xp3gZ9nkq7wDFTJqgJbC1SO7JjanS2JE2VXmhNmfGszozf62bhhvdNSguB+CdxlaqhdZC6uMXhk1LNUEYU6Y8+5TKGzvutuRrYSjf8Yait58ooyeKRYE/MObcBbaaw==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=iastate.edu;
  • Suggested_attachment_session_id: 2c515093-7433-1d5c-142b-2da87b73a135
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.


  • 2022 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the python-users archives: