text_combined: zooko kakltzookocom apr 8 2008 941 pm phillip j eby wrote im curious actually read pep 262 detail read though fine detail didnt write planning reinvent apt wrote programmers hear pep exclaim planning reinvent apt matter perception marketing value want gain python packages value critical mass good programmers using compatible tools code reuse lot programmers hate idea doesnt matter details isnt going provide value think part disagreement talking two overlapping use cases programmer sysadmin end user much like sysadmin time interested sysadmin use case ive mentioned sysadmin needs currently well satisfied apt sometimes gnu stow fellow sysadmins work absolutely going relax aptonly policy forseeable future use tool unless named apt written debianubuntu hand interested programmer use case setuptoolseasy_install already works pretty well already close achieving critical mass good programmers recently several packages project 1 relies become easy_installable twisted pywin32 thanks pje foolscap several bugfixes make work better easy_installsetuptools nevow zopeinterface patches queue make another one compatible setuptools pyflakes 2 3 setuptoolseasy_install already slowly winning want accelerate process reducing degree incompatible inconvenient objectionable programmers pep 262 sounds like nonstarter 1 appears backwardsincompatible setuptools easy_installeggs thus losing recently gained cooperation mentioned previous paragraph 2 defines new database file would prefer either away database files entirely relying filesystem alone hold information b continuing use current pth database file format possibly improved native support pth files python import machinery 3 2 triggers programmers exclaim planning reinvent apt thus making unlikely new proposal recapture cooperation setuptools already slowly gained im sorry pje know must frustrating proposal criticized social rather technical grounds social benefits seeking right perhaps pep 262 proposal actually alternatives complementary object python maintaining database installed packages although rely upon behavior least maintaining backwards compatibility python 24 least next several years python 25 least next several years want already implemented tested deployed code reuse features setuptoolseasy_install widely accepted best easily achieved fixing two frequent objections setuptoolseasy_install 1 cant conveniently install arbitrary directory 2 subverts meaning pythonpath regards zooko 1 httpallmydataorgsourcetahoetrunkdocsinstallhtml 2 httpdivmodorgtracticket2535 3 httpdivmodorgtracticket2048 _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 045728 0700 pythondev distutils easily consume parts eggs good