OK, just thinking through a little what it would mean to have an installation tool in Python core...<br><br>On Thu, Apr 16, 2009 at 5:08 PM, Tarek Ziadé <span dir="ltr"><<a href="mailto:ziade.tarek@gmail.com">ziade.tarek@gmail.com</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">> But then I don't think Python should have a built-in installer or package<br>
> manager. There are excellent tools already available (Buildout, pip, dpkg,<br>
> RPM), it would be better if we guided people to these tools and let them<br>
> pick the right one for their installation use case.<br>
<br>
</div>I wouldn't put zc.buildout in the same level than pip or easy_install.<br>
and I guess what we would have in DIstutils would be quite similar to<br>
what easy_install or pip offers.<br>
<div class="im"></div></blockquote><div><br>I think there are questions about scope. zc.buildout does more than pip, and pip does more than easy_install. I think easy_install has some important usability problems, otherwise I wouldn't have written pip. pip on the other hand has features that extend its scope in ways that might make it hard to include in the standard library. For instance the version control support, requirement files, bundles, and some miscellaneous functionality like zipping. Some of that could be separated out, though the version control support is more difficult. <br>
<br>Also it really mostly makes sense in the context of virtualenv. I'm strongly considering having an interactive warning if you try to install something with pip into the global site packages directory. PYTHONUSERBASE is an okay solution (not great, but okay), so I don't think this is contingent on something like virtualenv being standard... but it would help. I'm not sure how I'd pursue the virtualenv concept in Python core, as it's more a question of the concept of virtualenv than the implementation itself, but if there was general interest I could try.<br>
<br>Anyway, it seems odd to me to include a tool that hasn't been written yet, when there are tools that are being used and developed. OTOH, the only tool that is stable enough (not just bug wise, but stable as in isn't-changing) is easy_install. But while pip uses setuptools, it doesn't use easy_install at all, so including easy_install would really only make pip development harder.<br>
<br>That said, there might be parts of pip or easy_install which would be useful. I'm not sure what those would be though.<br></div></div><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>