What does it mean when a package is installed as "non-active development"?

Question

For whatever reason, my build system isn't installing one of my packages properly. When I use yolk (from within a virtualenv), I get the following:

bin/yolk -l elig
elig            - 3.1.2.dev    - non-active development (/home/jason/src/interface_dev/elig)

How exactly does a package go from active development to non-active development?

Probably means the package is no longer in active development? ;) — Bartek, Jul 06 '10 at 15:22
@Bartek - Well sure. But what does non-active development mean? :-) — Jason Baker, Jul 06 '10 at 15:25
Have you found an answer to this Jason. I'm quite curious as well. — Mridang Agarwalla, Jul 07 '11 at 11:04
Labels "active"/"non-active" and "development" are unrelated and refer to different things. I believe Development means the package is not installed inside site-packages but it has a link to another location (e.g. an egg-link file). — Carles Barrobés, Dec 19 '11 at 22:01

score 5 · Answer 1 · answered Jan 12 '12 at 17:22

Looking through yolk source I found this:

*"The following options show information about installed Python packages. Activated packages are normal packages on sys.path that can be imported. Non-activated packages need 'pkg_resources.require()' before they can be imported, such as packages installed with 'easy_install --multi-version'. PKG_SPEC can be either a package name or package name and version e.g. Paste==0.9",

for non activated i found: *'List non-activated packages installed by distutils or setuptools. Use PKG_SPEC to narrow results.'

and for activated: *'List activated packages installed by distutils or setuptools. Use PKG_SPEC to narrow results.'

Hope that satisfies your needs or atleast helps you ;). There seem to be very little documentation on this online.
* found in http://trac.assembla.com/yolk/browser/trunk/yolk/cli.py

What does it mean when a package is installed as "non-active development"?

1 Answers1