This is what I came up with. I can set the PYTHONPATH in the .bashrc file and it will be set for the Bash console. And the PYTHONPATH will be inherited by the Python process executed from the Bash command line but the import function still doesn't find the module.
The PYTHONPATH can be set for Python interactive mode, a Python console, by setting it in the .pythonstartup.py file. But still can't import a module.
What does work is to click 'Open Bash console here' when in the directory that the module resides in (under the Files tab). And starting Python from the command line.
Easier way to get it to work is to place the module in the site-packages directory. For me that is in /home/DanCarroll/.local/lib/python3.5/site-packages.
Another option that works while leaving the module in a sub-directory other than site-packages is to make use of the init.py file. Place empty copies of init.py in each directory leading to your module from your home directory.
Here is what worked for me and my directory/file layout.
/home/DanCarroll
.
| - - PythonCourse
| | - - __init__.py
| | - - Chapter9
| | - - __init__.py
| | - - MyLibrary.py
To import the module from the Python shell, type
>>> from PythonCourse.Chapter9.MyLibrary import *