Lines Matching refs:WorkingSet

117         WorkingSet
179 ``WorkingSet`` Objects
182 The ``WorkingSet`` class provides access to a collection of "active"
183 distributions.  In general, there is only one meaningful ``WorkingSet``
188 ``sys.path``, and therefore may wish to create other ``WorkingSet`` instances.
199 ``WorkingSet(entries=None)``
200     Create a ``WorkingSet`` from an iterable of path entries.  If `entries`
204     Note that you will not normally construct ``WorkingSet`` instances
222 Basic ``WorkingSet`` Methods
225 The following methods of ``WorkingSet`` objects are also available as module-
290 ``WorkingSet`` Methods and Attributes
294 working set, so they must be explicitly invoked on a particular ``WorkingSet``
301     called by the ``WorkingSet()`` constructor during initialization.
311     True if `dist` is active in this ``WorkingSet``.  Note that only one
312     distribution for a given project can be active in a given ``WorkingSet``.
421    ``WorkingSet`` this method is called on, which will typically mean that
765     the section above on `Basic WorkingSet Methods`_ for more information.)
868 Most commonly, you'll obtain ``Distribution`` objects from a ``WorkingSet`` or
869 an ``Environment``.  (See the sections above on `WorkingSet Objects`_ and
1127 distribution is added to the ``WorkingSet`` and ``sys.path`` if one was not
1729    method to ``WorkingSet``, and the ``__add__()`` and ``__iadd__()`` methods
1762  * Fixed a problem with ``WorkingSet.resolve()`` that prevented version
1795  * Fix a bug in ``WorkingSet.resolve()`` that was introduced in 0.6a3.
1870      ``WorkingSet`` instead, and the ``best_match()`` method now uses a working