Comments on: Switching to pip for Python deployments http://blog.mozilla.org/webdev/2013/01/11/switching-to-pip-for-python-deployments/ Engineering the web Fri, 17 May 2013 21:43:21 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Luper Rouch http://blog.mozilla.org/webdev/2013/01/11/switching-to-pip-for-python-deployments/comment-page-1/#comment-227692 Luper Rouch Wed, 23 Jan 2013 21:04:22 +0000 http://blog.mozilla.org/webdev/?p=3163#comment-227692 I made a script to ease the creation of ‘frozen’ requirements files: https://github.com/Stupeflix/freeze-requirements

]]> By: Anders Pearson http://blog.mozilla.org/webdev/2013/01/11/switching-to-pip-for-python-deployments/comment-page-1/#comment-227613 Anders Pearson Mon, 21 Jan 2013 03:17:41 +0000 http://blog.mozilla.org/webdev/?p=3163#comment-227613 This is pretty much the approach that I’ve been employing and advocating for the last few years. (see this post: http://ccnmtl.columbia.edu/compiled/sysadmin/deploying_django_and_deploying.html)

I go one step further and actually check in the packages for the dependencies (as tarballs) in the same repo as my project and use (essentially) “pip -E ve –index-url=” –requirement requirements.txt” to force it to install *only* from those packages and never try to contact any remote server during the deploy.

That bloats the repos a little bit (30-40mb for a typical Django app), which I’m OK with, but has the advantage that deploys have no dependencies on external servers and I can bootstrap a project on my laptop without an internet connection, which has proved invaluable many times.

So congrats on getting away from dreaded recursive submodules.

]]>