Just to follow up on this. I assume that using PyFerret built for your system (either through an Anaconda or a Homebrew build) has fixed the issues with finding the libraries from a previous discussion thread.
For PyFerret Python users using Jupyter notebooks:
Jupyter notebooks started from JupyterHub do not normally have user's environment variables (such as those set in $HOME/.bashrc) for Python sessions. If the PyFerret environment variables are not assigned in your Jupyter notebook, one can use the pyferret.addenv method with just the arguments FER_DIR= (path to pyferret installation directory) and FER_DAT= (path to datasets directory) to assign the default values. There is also a pyferret.addpath method that adds to the environment variables just like the Faddpath command.
However, the pyferret module needs to be found in order to use these pyferret methods. If the pyferret module is not found when importing, then its location needs to be added to sys.path. So something like the following, where ferdir is the (string) location of the PyFerret installation and ferdat is the (string) location of the datasets directory:
sys.path.insert(1, '%s/lib/python%d.%d/site-packages' % (ferdir, sys.version_info, sys.version_info))
pyferret.start(journal=False, quiet=True, unmapped=True)