zooko kakltzookocom folks way pleasure meet many real life first time pycon want 1 standard python build tools default produce machine parseable package metadata include package dependency information reasonably welldefined semantics oh good already since distutils python 25 produces egginfo metadata easytoparse format 2 machineparseable metadata widely supported understood python community retrospect bad isnt named pkginfo instead egginfo order avoid fraught politics around concept eggs concrete example misunderstanding sad fact many linux distributions habit deleting information python packages perhaps impression obviated packaging tools major distributions stopped unifying createdbydefault pkginfo files createdby default egginfo directories would nice 3 standard python library includes tool find parse metadata write programmatic tests dependencies like httpallmydataorgtractahoebrowser_auto_depspyrev2062 one improvements anticipating pkg_resources going standard library 4 standard python library includes tool find read resources python modules came bundled python package consider example snippets code nevow httpdivmodorgtracbrowsertrunknevowsetuppyrev13786l10 httpdivmodorgtracbrowsertrunknevowsetuppyrev13786 httpdivmodorgtracbrowsertrunknevowsetup_eggpyrev2406 nevow uses pkg_resources import files defaultcss able find runtime even imported py2exe py2app zip platforms homegrown setup script homegrown find file function fail using pkg_resources setuptools install makes test_nevow pass allmydataorg buildslaves httpallmydataorgbuildbotwaterfallshow_eventsfalse regards zooko _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom tue 05 aug 2008 073053 0600 pythondev distutils pep 365 adding pkg_resources module