I added a new class and it will not see it since it looks like gh Python component somehow stored the first iteration of the module. Thank you, However, if you are seeing old behavior, it is likely that you have two copies of the same script, and the old one is loaded before the new one is found.
Make sure that the module you want to use is loaded from the right location.
Its a library that I am developing so I am still making a lot changes to it.
I wanted to test it in GH but once loaded in there seems to be no way to refresh it.
The problem starts with two things: something Python does implicitly, and Django's project layout. This breaks when you deploy, because typically you don't run -- at least, not from within your project directory.
Now is the point people find they've been writing all of their apps and code with this assumption .... It's usually caused by your code importing the same module by two different "names". The de-facto practice of DJANGO_SETTINGS_MODULE=projectname.settings make clear sense, now, since there it is, right in your workspace.
To fix the problem it, the "Python Path", just needs to be added to the system.
Among common Python exceptions, the most infamous and time consuming one to solve is no doubt the “Module Not Found Error” but actually is pretty simple to fix once you understand a couple of concepts.
This is done through the inclusion of a "System Variable", commonly called the "Python Path".
Essentially the variable is a collection file locations, details to different key components and modules of the API, for example a typical Python Path might appear similar to the following when the Python API has been installed to "C:\Python22\"; Design note: the actual path will vary depending upon Python installation location and whether any version numbers are used - typically because more than one iteration of the software might be in place.
and suddenly, you're getting errors about your apps not existing. Python keeps a list of directories in which to search for your modules when you "import" them.
Some helpful person on #django tells you it's because your PYTHONPATH isn't set right. You can see the default list with these dirs, it means if you set PYTHONPATH to "/foo/bar" and try "import baz", Python's going to look for /foo/bar/baz/ or /foo/bar/.