guido van rossum hoaufpythonorg tue mar 18 2008 336 pm phillip j eby wrote 0343 pm 3182008 0500 guido van rossum wrote people would care writing setup script works bootstrap module basically package manager implementers thats true today sure soon widely available others sure want use want brightline distinction isnt bootstrappable rather murky region maybe youre anything complicated anything uses distutils setuppy doesnt external dependencies see horribly incomplete prototype added sandboxbootstrapbootstrappy wrote plane last night tested file urls needs add ability consult pypi find download url probably ps also managed successfully install setuptools source giving url gargz file seems misunderstanding proposing instead boostrap installer powerful enough allow used install real package manager like setuptools pep 365 proposed downloading archive cache directory optionally running something explicitly disavows installation anything since downloaded archive wouldnt added syspath except duration bootstrap process scripts installed indeed apart methods would used locate archive pypi determine run inside nothing particularly eggspecific proposed bootstrapping process bootstrappy exactly downloads unzipsuntars file runs setuppy install command line argument currently looks setuppy toplevel one level deep unpacked archive course likely root administrator run effectively fully eggneutralize bootstrapping approach need know locate appropriate archive determine run right latter could use alreadyin26 convention running __main__ zipfile directory bad distutils source distributions extra directory name embedded one cant execute directly otherwise couldve let people drop __main__py next setuppy otoh maybe would enough use setuptools algorithm finding setuppy locate __main__py im fairly sure briefly expressed pep whats wrong running setuppy install id rather continue existing standards conventions course wont work setuppy requires setuptools old style setuppy files use distutils work great managed install django file url open question naming convention version detection bootstrap tool identify files listed pypi suitable use regard version selection file type however pypi grow support designating appropriate files andor versions way wouldnt need naming convention dont understand pypi well seems poor design browsing via keywords emphasized easy way search keyword list packages emphasized enough main page occurs side bar main text assume theres programmatic api xmlrpc havent found yet without one bootstrap tool would grow version parsing scheme type play guessing games file extensions one reason limited pep 365s scope downloading eggs actually uploaded pypi rather arbitrary packages linked pypi two version parsers distutils referenced pep 345 pypi 12 metadata standard propose something right would inclined propose using setuptools version parsing semantics interpretation alphabetadevetc releases point code advantage distutilsversion bdist_bootstrap format thats essentially bdist_dumb zip file internal path prefixes stripped making importable zip different file extension maybe pybootzip filename convention would use setuptools canonicalization escaping names version numbers allow unambiguous machine parsing filename __main__ module would present archive run opposed downloaded temporary directory hm use existing convention running setuppy unpacking works great experience advantage easy fallback end manually whatever reason calling bootstrap module bootstrap python bootstrap projectname optionalversion module would expose api allow used programmatically well command line bootstrapped packages use bootstrap process locate dependencies desire todays package management tools least based setuptools present theyll need download beginning bootstrapping process sounds like going beyond bootstrapping vision use bootstrap module command line suggest install setuptools alternate package manager choice use easy_install whatever alternative install rest apart keeping pep selfcontained short anything think would object may reserve right course later like something details setuptools versionfilename rules ive put pep really anything else im asking theres anything thats obviously offensive point spend time new pep id love could write point code takes package name optional version returns url source archive type case cant guessed filename contenttype header guido van rossum home page httpwwwpythonorgguido _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 081409 0700 pythondev pep 365 adding pkg_resources module