On Mon, Jul 20, 2015 at 4:05 PM, Iain Duncan <[email protected]> wrote: > Hi, we're embarking on a project that will stitch together many apps, and I > figured I should do my due diligence on hunting for the state-of-the-nation > in python build tools. I've personally used buildout in the past and liked > it, but I know for other team members something that was more pip/virtualenv > based would be preferable. Just curious what folks are using?
I use pip/virtualenv. It mostly comes down to the person's background. Pip/virtualenv appeals to those who like to learn and try out things interactively, because the pip install/uninstall process is like an interative Python session: you can install (~= import) things one at a time to try them out, and uninstall (~= del) it if you don't like it.... and eventually you have your entire stack installed and you just have to remember to list the packages in setup.py or a requirements file, and "pip freeze" can help with that. In contrast, with buildout you're essentially recreating the environment every time you want to add or change something, and that's a foreign concept to some people. Then there's the recipe syntaxes, and the fact that only one or two of them are relevant to 99% of the packages these people would use, it seems like unnecessary overhead. On the other hand, i;m told that buildout is more flexible and can do a wider variety of installation tasks, and it may be philosophically better for production deployments, so there's that. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
