3 ms·

"Too often when coming to a new language, it's hard to know what is old and busted and what the future is." This is too true. As a Python/Django newcomer that

"Too often when coming to a new language, it's hard to know what is old and busted and what the future is." This is too true. As a Python/Django newcomer that has been difficult. Any perspectives on buildout and where it fits into the toolbox of the future? I started using it after watching Jacob Kaplan-Moss' Django Deployment Workshop ([1] -- highly recommended) and I like it, but I read about virtualenv and pip much more often. [1] http://python.mirocommunity.org/video/1689/pycon-2010-django-deployment-w http://python.mirocommunity.org/video/1689/pycon-2010-django... One thing I don't really get about Python deployment tools in general is the idea of building eggs for everything, especially the parts of my own applications that I will never redistribute. This seems to be emphasized with all the tools.

po 16y ago
I have never personally used buildout so I can't speak about it pro or con. It always seemed a bit heavy handed to me but that's an uninformed opinion. I also think the idea of packaging to egg files is somewhat unneeded. When I use pip, I use cheeseshop for the more established frameworks I depend on (Django, south, etc...) but I also use pip to pull directly from various git repos. When I package my own projects for use, I just drop a setup.py script in there and then install from github using pip. Looking at my requirements.txt for my main project, I have about 10 dependencies from cheeseshop and about 10 pulling from various git or bitbucket repos.