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 03:45:48 +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=vgLm5PWa3Mf4l8+mCe/1lTB8U5iWJyNoOIQ0MB/nnjg=; b=Tq3zZ6+zPEh9OXXeqRMJyuKhffAWvAdzr0uXLzV7g56e4GPgmipQe0kmTdFF9ouM5k7A9s3VQT7ttNxe5j/VnnS7QVUtRV7Y6eiNoHKOXaM2pJERzZU8q5JE+tz1/zr7CjS2T07ZGtzefJ4nZC5MtplbakC+2rs0zzb7F42musHwd5eNkDuEDLtyOTCtM+Gnkvib1fKflQPxIDvYr7EuuDdJV3OcAmzohIrVsHqvAIGr94erwzIct4+dYdiUW8YDSR4T50uOGmnwSXgx0+4tvdJezG2NSmBeN1K4S/nQSlkOE4VIDnwz1JRlK6HXf0hxMbeYsA1+Pu45crr4WnbcOA==
• Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ciX7V0AMNgshAgh+TVB2ubVpPXRg2IG5vo+/8yY1Un03FBOCgCvTgAB6+VWFptXm8d6uMI9x7tQTdW7v07cdx1GU1lVjHGMXGWbuUduRCuDr/jSB4Cs+jiyxto3x0xOj2rqqtWdtlLRJdbvJjxklAoXDSJHIaRU1zRIp8zpGAPSdG/XdGqKSXFRFfnX4A+KOVlsdXCjCliVCvULlZWbST7v4j7silCDukkgqfthFEr8LYyVnNkvWH5T898bp/8wQmrR1nGg15L9r0CJqevKkItCjQgf8ZVNpdUFWSRz8en3dKnDd0aoyBIdm9CgSr39wzMaQaPuDw2B8E0lb9Wu2Xg==
• Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=iastate.edu;
• Suggested_attachment_session_id: d77a69ce-e23c-a559-2a53-8b84fbbae088

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/__init__.py: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.

• Follow-Ups:
  • Re: [python-users] miniconda error message
    • From: Weber, Jim

• References:
  • [python-users] miniconda error message
    • From: Weber, Jim