text_combined: apbrcdivmodcom 0349 hoaufpythonorg wrote stand corrected points youve convinced lib wrong still dont like local last place local dot files directories symmetry usrlocal pretty weak certainly wont help beginning users say symmetry weak name might evocative main thrust im saying autotoolsstyle directory layout symmetry suggest exactly sense thats usrlocal dont actually care except many others already use local value software honors better gnu stow arguably king peruser installation management suggests local autotools prefix target free desktop project implicitly suggests local suggesting localshare place put files would normally searched usrshare usrlocalshare word local floating around meme space dont like word much dont see theres different one clearly evokes concept either originally used unix unix switched local noticed folks one ive actually seen mentioned times nixconfig certainly dont think better would help beginning users localbin locallib honored system adherents idea would nice users could install source without admin privs suggesting distro guys figure years somebody might bite happens start easier build stuff source separated location need root stomp system inevitably break stuff agitating pythonplatformlibraries ld_library_path equivalent lot harder straight face reason im bothering spill many pixels topic think would great python first real adopter convention one project really gone full bore subsequent one progressively easier convince however youve made mind python think ive made case point ill stop cluttering lists way worth _hate_ binlibetcmansrcinclude naming convention mess mess programmatically honored like hundred billion lines code want supported hidden compromise im okay python would like able say user explicitly set environment variable order benefit feature like pythonpath pythonstartup might defeat point making easy use noobs another point seems change entirely shared conventions works default behavior going set environment variable set pythonpath already much flexible python opens new problems though although perhaps trivially resolved interoperate distutils make python setuppy user python setuppy prefix local would pretty straightforward python would need new convention python pythonscripts directory one could add path pythonplatform directory includes libraries random junk like manpages html docs python26lib python26lib fair separate purposedesigned python directory layout might also make certain things neater example one could support parallel installation python26 python26 giving lib bin directory always scripts 26bin dir invoke 26 interpreter rather separated space libraries mangle names scripts twistd80py26 id still prefer compatibilitybyconvention tools languages etc though long term everyone followed suit local would great dont want python java ruby php perl ocaml erlang path long arm run applications without systeminstalling os x think put somewhere library put different place python framework puts stuff isnt whole point place current python releases os x already functionality via librarypython25sitepackages also id strongly suggest supporting library although existing location seems fine whatever default platforms already enough points pain os x behaves kind like unix really every project needs add little workarounds caveats documentation benefit derived making situation worse introducing another subtlety _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom fri 08 aug 2008 074344 0000 pythondev python3000 reminder last alphas next wednesday 07may2008