Sorry, I havent kept this updated as I pursued the matter.
This seems to be where I am at:
PythonAnywhere seems to be calling the old module over the new module for this specific package. Other modules installed the same way are working without hitch. If I run python from my virtual machine bash console, I am able to call the package without error.
Overview of what I've done to investigate:
My web app is using python 3.4. I had thought 3.3 was pips version number and had seen it recommended online for a similar issue.
I did
that displayed the same results as
Not really sure what the difference is, but I uninstalled everything using pip uninstall and that went smoothly.
pip uninstall flask_httpauth
#... success
pip3.4 install flask_httpauth
I then went and looked in my venv site packages to find the source file. Upon opening the file, I can see that I should be able to import HTTPTokenAuth from the package.
I went back to the bash council I opened to my virtual environment, and opened python. Python 3.4 loaded. I then called the module as shown below, and it worked without error.
from flask_httpauth import HTTPTokenAuth
During this process I completely deleted my previous virtual enviorment. I found that I was missing necessary modules that caused errors since they were now missing. I installed those in the same console using
Which got everything that was working working again. This suggests to me that I am installing flask_httpauth the proper way, but something is wrong still.
The developer of the package commented on my stack overflow post suggesting I may be using an older version.
"Hard to know why, but my guess is that you are installing the upgrade on one virtualenv, then using another when you run your application. Do you have a shebang line on your start up Python script? Check which Python interpreter you have in there, make sure it goes to the right virtualenv"
I am not using a shebang. I am using the area of the web tab dedicated to virtual enviorments.