[01:42:04] ** pythonhead has left IRC ("Client exiting")
[04:02:44] [connected at Sat Aug 20 04:02:44 2005]
[04:02:44] <> *** Looking up your hostname...
[04:02:44] <> *** Checking ident
[04:02:44] <> *** Found your hostname
[04:03:18] <> *** No identd (auth) response
[04:03:18] <> *** Your host is calvino.freenode.net[calvino.freenode.net/6667], running version hyperion-1.0rc5
[04:03:18] [I have joined #peak]
[10:45:41] ** pythonhead has joined us
[13:11:34] ** pje has joined us
[13:11:50] <pje> pythonhead, FYI, you should read pkg_resources.txt in CVS to learn about the API
[13:11:57] <pje> in particular, find_distributions(path_item)
[13:12:03] <pje> and the stuff on the metadata API
[13:12:30] <pje> Also, the Environment class is an index of installed packages by project name
[13:12:32] <pythonhead> Thanks, I'll look at that. I'm kind of stumped. I tried, find_byfile I think, but couldn't get the metadata
[13:12:56] <pje> You don't want to use stuff that's not in the documentation like that.
[13:13:10] <pje> Just create an Environment object
[13:13:18] <pythonhead> Ok, I'll grab the cvs and start reading
[13:13:23] <pje> It's like a dictionary from project name to a list of installed Distribution objects
[13:13:40] <pje> The Distribution objects have methods like get_metadata(name), has_metadata(name) etc.
[13:13:58] <pje> Really, if you want all the eggs on sys.path, you can write something like:
[13:14:03] <pje> env = Environment()
[13:14:08] <pje> for project_name in env:
[13:14:18] <pje>     for dist in env[project_name]:
[13:14:25] <pje>       print dist
[13:15:02] <pje> If you want to print the distribution's dependencies, print dist.requires()
[13:15:29] <pje> Anyway, the docs for Environment, Distribution, and the metadata API should be the most relevant bits.
[13:16:02] <pythonhead> Great, thats going to help me get started, thanks
[13:16:19] <pje> no problem; I just popped in 'cause I saw your question from yesterday.
[13:16:24] <pje> Gotta run.
[13:16:43] ** pje has left IRC ("Client exiting")
[13:17:16] ** pje has joined us
[13:17:21] <pje> Oh, forgot to mention...
[13:17:34] <pje> If you want to know which distributions are *activated* on sys.path, you want the working_set
[13:17:39] <pje> i.e.:
[13:17:45] <pje> for dist in pkg_resources.working_set:
[13:17:48] <pje>     print dist
[13:18:15] <pje> i.e., those are the ones that have been put on sys.path because of a .pth file or have been require()d to this point, etc.
[13:18:23] <pythonhead> Gotcha
[13:18:30] <pje> WorkingSet objects track a set of activated distributions
[13:18:41] <pje> Environment tracks *all* distributions in the directories on sys.path
[13:18:55] <pje> (or whatever paths you give to the WorkingSet or Environment constructors, that is)
[13:19:08] ** pje has left IRC (Client Quit)
[16:01:41] ** erikrose has joined us
[17:20:12] ** erikrose has left IRC ()