It's all controlled by /etc/profile.d/awips2.sh (and awips2.csh).
In that file there is a catch for root (
https://github.com/Unidata/awips2/blob/unidata_18.1.1/rpms/awips2.upc/Installer.awips/scripts/profile.d/awips2.sh#L16)
not to source the AWIPS env vars beyond that point to avoid conflicting
Python environments (and thus yum). You can add a similar catch for your
own user account and prepend /usr/lib64 to the paths (I think that will
work), or you can move the contents of the file to the top of the
/awips2/cave/cave.sh script and see if that works (I have not tried).
Michael James
Unidata Program Center
Boulder, CO
On Sat, Feb 2, 2019 at 7:16 AM G Schuck <gschuckle5@xxxxxxxxx> wrote:
> Every time I install, reinstall Cave, my Python environment gets
> clobbered. Is it something on my end? Pip and QGIS break... uninstall Cave
> and they work. 'Which' python reveals /awips2/python/bin/python, instead of
> my usual /bin/python. Pulling my hair out.
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> awips2-users mailing list
> awips2-users@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
