<br><br><div class="gmail_quote">On Fri, Mar 21, 2008 at 2:47 PM, Phillip J. Eby <<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Second, there were no uninstall tools for it, so I'd have had to<br>
write one myself. (Zed's "easy_f'ing_uninstall" to the contrary, it<br>
ain't easy, and I have an aversion to deleting stuff on people's<br>
systems without knowing what will break. There's a big difference<br>
between them typing 'rm -rf' themselves, and me doing it.)<br>
</blockquote><div><br>Agree. I tried a while ago to write a "easy_uninstall" but this<br>is not possible from an application-point of view, to do clean things.<br><br>zc.buildout resolves this by installing eggs locally, to an isolated<br>
environment, so my main Python installation doesn't hold any extensions<br>at all.<br><br>So if a database of installed package is created, I would be in favor of <br>an application-oriented system where it is possible to create, update, install,<br>
a set of packages dedicated to an environment (default would be Python). <br>Maybe by having a namespace tied to a list of versions.<br><br>In other words; having the same feature virtualenv provides, in Python<br>itself, and define somehow how to switch to it.<br>
<br>$ easy_install the.package --environment MyApp<br> <br><br></div></div>