Pythonpath not updating sys path
Keep those puppies in their warm, snuggly project subdirectories.
This way you can also initialize that project folder (i.e.
You will need to replace directory names like This will only affect the path in the current Python session.
If you quit and restart, you will need to add the path again.
is constructed as a concatenation of (1) the current working directory, (2) content of PYTHONPATH environment variable, and (3) a set of default paths supplied by the installed Python interpreter.
If the module you are trying to import is not found in any of the directories defined in Alternatively, you can add the custom module directory in PYTHONPATH environment variable, which will augment the default module search paths used by the Python interpreter.
These methods will allow you to access modules without copying or moving files into your working directory, and you can easily access modules you write yourself or modules you download from the Web.
None are extremely complicated, but the last two require working with the command line and editing startup files on your operating system.
If you are unfamiliar or uncomfortable with this, you might prefer the first two methods.
In order to reproduce the exception, let’s consider a project structure like: So far, so easy…
but let’s go on with scenario N.2 This one occurs when we are executing a python script with an import statement in a directory from which the interpreter cannot resolve the path to the required module defined in the import statement due to missing or bad configuration of the This one is the most hateful that you can face.
You will need to quit Spyder and restart or “Restart Kernel” for the changes to take effect.