Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 1a54d71

Browse files
committed
Mention that .pth files can't be used to override standard modules
(suggested by Jack Jansen)
1 parent 2095c06 commit 1a54d71

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

Doc/inst/inst.tex

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -728,10 +728,14 @@ \subsection{Modifying Python's Search Path}
728728
directory that's already on Python's path, usually to the
729729
\file{.../site-packages/} directory. Path configuration files have an
730730
extension of \file{.pth}, and each line must contain a single path
731-
that will be added to \code{sys.path}. Paths can be absolute or
732-
relative, in which case they're relative to the directory containing
733-
the \file{.pth} file. Any directories added to the search path will
734-
be scanned in turn for \file{.pth} files. See
731+
that will be appended to \code{sys.path}. (Because the new paths are
732+
appended to \code{sys.path}, modules in the added directories will not
733+
override standard modules. This means you can't use this mechanism
734+
for installing fixed versions of standard modules.)
735+
736+
Paths can be absolute or relative, in which case they're relative to
737+
the directory containing the \file{.pth} file. Any directories added
738+
to the search path will be scanned in turn for \file{.pth} files. See
735739
\citetitle[http://www.python.org/dev/doc/devel/lib/module-site.html]{the
736740
documentation for the \module{site} module} for more information.
737741

0 commit comments

Comments
 (0)