I find it easier to use the following, since it makes it clear if the empty string ('') is in the path: python -c "import sys, pprint; pprint.pprint(sys.path)" ( And I found this answer more helpful, too; the title of the question mislead me into thinking it was about the actual path python was using, rather than the contents of the PYTHONPATH environment variable.)

Mar 15, 2009 · Fortunately, typing path at the windows path let me find where I had installed it. The path was an option when I installed Python which I just forgot. If you didn't select setting the path when you installed Python 3 that probably won't work - unless you manually updated the path when you installed it.

Here is what I learned: PYTHONPATH is a directory to add to the Python import search path "sys.path", which is made up of current dir. CWD, PYTHONPATH, standard and shared library, and customer library.

Feb 29, 2012 · PYTHONPATH = If this variable exists in your environment, Python will add it to the normal search path for modules when you use any import statement; you normally do not modify this as well behaved Python scripts will install themselves in the site-packages directory, and Python searches this by default. PATH = this is the global file system ...

Sep 13, 2010 · The question isn't about the PATH that DOS uses to find commands, but the Python path, i.e. sys.path in Python. In most operating systems, Python just uses the system environment variable PYTHONPATH, but Windows seems to be 'special'. –

However, the best practice is to use the os.path module functions that always joins with the correct path separator (os.path.sep) for your OS: os.path.join(mydir, myfile) From python 3.4 you can also use the pathlib module. This is equivalent to the above: pathlib.Path(mydir, myfile) or: pathlib.Path(mydir) / myfile

The following program will add the python executable path and the subdir Scripts (which is where e.g. pip and easy_install are installed) to your environment. It finds the path to the python executable from the registry key binding the .py extension. It will remove old python paths in your environment. Works with XP (and probably Vista) as well.

The same can be accomplished with path.walk() as pointed out by others, but 1) this works on versions earlier than Python 3.12, and 2) this immediately yields Path objects instead of having to manually assemble them from strings as one would have to with walk().

I tried python -c"import sys;sys.path.append('/my/dir')" and then python myscript.py mycommand, but it obviously doesn't share the path from the first interpreter session with the next. Ah, just saw your next comment, trying now... Didn't work on WinXP.

Jun 24, 2020 · Get the path of the parent folder, then os.join your relative files to the end. # get parent folder with `os.path` import os.path BASE_DIR = os.path.dirname(os.path.abspath(__file__)) # now use BASE_DIR to get a file relative to the current script os.path.join(BASE_DIR, "config.yaml") The same thing with pathlib: