Python3

[Mullen, Daniel J]

With FR 3.0.x and Python2, the python module didn't automatically register any system libraries.

In 3.2.6 with Python 3.9 (on RHEL9) the python3 module seems to automatically add the sys.path
And at the front of the path.
These first for are nowhere in my configuration but at runtime, that’s what the app reports as the path.

/usr/lib64/python39.zip
/usr/lib64/python3.9/lib-dynload
/usr/lib64/python3.9/site-packages
/usr/lib/python3.9/site-packages
# our code
/etc/raddb/mods-config/python3
# application specific packages
/etc/raddb/lib/python3.9/site-packages

And indeed, FR is using the packages out the the /usr/lig64

Is there a way to force the old behavior?
Namely that only the paths declared in python_path are included and in the order specified.

---------------------------------------------------------
Dan Mullen

----------------------------------------------------------------------
This message, and any attachment(s), is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/electronic-disclaimer. If you are not the intended recipient, please delete this message. For more information about how Bank of America protects your privacy, including specific rights that may apply, please visit the following pages: https://business.bofa.com/en-us/content/global-privacy-notices.html (which includes global privacy notices) and https://www.bankofamerica.com/security-center/privacy-overview/ (which includes US State specific privacy notices such as the http://www.bankofamerica.com/ccpa-notice).