text_combined: phillip j eby moetelecommunitycom 1001 482008 0700 zooko wrote mar 26 2008 734 pm chris mcdonough wrote zooko wrote httpmailpythonorgpipermailpythondev2008march078243html simple proposal make standard python import mechanism notice eggs pythonpath insert location syspath eliminates 1 problem eggs dont easily work installing places site packages allow installed system take precedence nonegg packages even explicitly put packages earlier pythonpath latter behavior disagreeable prorgammers sorry im loop theres subtlety im disregarding doesnt appear either issues mention actually problem eggs instead problems eggs get installed easy_install uses pth file extend syspath reasonable put eggs pythonpath manually eg syspathappendpathtosomeegg instead using easy_install install yes missing something many programmers lennart regebro posted thread find current eggs system perfectly convenient work many others glyph lefkowitz posted related thread find annoying actively ensure eggs ever allowed touch system reasons latter problem two 1 cant conveniently install eggs nonsystem directory mypythonstuff wha 2 allow even single egg installed pythonpath change semantics pythonpath way manually putting egg front pythonpath considered change semantics pythonpath problems directly caused need eggs hack sitepy python automatically added eggs found pythonpath syspath problems would go away add new ones skeptical current proposals define new database installed packages fare better current eggs scheme respect purpose installation database allow easy_install eschew use egg files directories anything multiversion installs thus need add egg files directories head pythonpath conflicts would handled install time rather runtime words skeptical prorgammers going willing use new database format already database filesystem already tools control mv rm pythonpath many already hate existence easy_instlalpth database file dont see new database file would different pep 262 propose database file proposes inclusion metadata file installed distribution proposal makes current benefits eggs clean easy code use among programmers compatible current tools mv rm pythonpath also forwardcompatible sophisticated proposals add features like uninstall operating system integration actually current proposal doesnt work unless least way indicate version egg automatically added syspath way change otherwise might well use option easy_install require eggs runtime needs neither pth files sitepy hacking meanwhile understanding people dislike eggs dislike install setuptoolsbased package installed egg default installation database proposal way people really read understand pep 262 including open issues trying compete allow setuptoolsbased packages install oldfashioned way default eggs similarly easy_install would able skip installing eggs unless wanted multiversion support people dont like eggs would never see since way youd ever get would via easy_install would never use way since posted proposal two weeks ago pointed couple python hackers currently refuse use eggs url httpmailpythonorgpipermailpythondev2008march078243html agreed made perfect sense told one alternate proposal define new database file contain list installed packages sighed rolled eyes said planning reinvent apt planning make possible easy_install overwrite things would break system allow distutils setuptools uninstall installed thats considerably less ambitious goal far _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 064633 0400 pythondev easily consume parts eggs good