Lines Matching refs:pth

157 Installed packages are added to an ``easy-install.pth`` file in the install
194 any previous version in the ``easy-install.pth`` file, so that Python will
409 scripts or .pth files.  You can then copy the contents of ``somedir`` to the
411 prevents .pth files from being used, ``-a`` means to copy all the eggs needed,
566 code added to the ``easy-install.pth`` file.  So, if you are using version
712     adding an ``easy-install.pth`` entry for the package being installed, and
897     "Site" directories are directories where ``.pth`` files are processed, such
899     automatically detects whether a given directory processes ``.pth`` files
903     supported ``.pth`` files.
968 and manages them using a custom ``.pth`` file in that same directory.
1121  * Fixed ``win32.exe`` support for .pth files, so unnecessary directory nesting
1150    ``.pth`` files.
1191  * Fixed a problem with ``.pth`` testing on Windows when ``sys.executable``
1254    ``easy-install.pth`` file is already in use there.
1256  * Construct ``.pth`` file paths in such a way that installing an egg whose
1281  * Use relative paths in ``.pth`` files when eggs are being installed to the
1282    same directory as the ``.pth`` file.  This maximizes portability of the
1300    for ``.pth`` file support, and directory writability/existence checks.  This
1344  * Fixed ``.pth`` file processing picking up nested eggs (i.e. ones inside
1345    "baskets") when they weren't explicitly listed in the ``.pth`` file.
1382    that makes the PYTHONPATH-based approach work with .pth files, so that you
1444    Made ``easy-install.pth`` work in platform-specific alternate site
1449    from the ``easy-install.pth`` file.