Lines Matching refs:pth

52 isn't necessary to create ``.pth`` files or otherwise modify
561 environment variable, and ``.pth`` files.
564 environment variables, this leaves ``.pth`` files as EasyInstall's only
567 But ``.pth`` files are rather strictly limited in what they are allowed
573 directory, because they can't create a ``.pth`` file that Python will
576 contain ``.pth`` files, they won't be able to install newer versions of
582 The first is that EasyInstall leverages ``.pth`` files' "import" feature
584 to a ``.pth`` file will always appear before both the standard library
586 possible for a user who can write a Python-read ``.pth`` file to ensure
595 afterwards it processes any ``.pth`` files found in ``PYTHONPATH``
599 ``.pth``-prescribed sequence.
607 2. All eggs installed by EasyInstall in any ``.pth`` file in each
609    then normal ``.pth`` processing order (which is to say alphabetical
610    by ``.pth`` filename, then by the order of listing within each
611    ``.pth`` file).
613 3. All eggs installed by EasyInstall in any ``.pth`` file in each "site"
619 5. Any paths from ``.pth`` files found on ``PYTHONPATH`` that were *not*
624    of any ``.pth`` files found in the "site" directories.
628 section 5 emulates what the "normal" semantics of ``.pth`` files on
632 well as notes on the actual magic inserted into ``.pth`` files to make