On Tue, Feb 21, 2012 at 1:24 PM, Sébastien Billion <sebastien.bill...@gmail.com> wrote: > Hi, > > Set a virtualenv is good thing. You can write a shell script which set the > virtualenv and install all the external module with pip -r. Use pip -r > nameofrequriementsfile.txt. In this file, put the list of module with > version. > Exemple: > django==1.3 > PIL==1.1.7 > > If you want distribute your own apps, submit them on Pypi > http://wiki.python.org/moin/CheeseShopTutorial >
A more realistic proposal for proprietary packages is to bundle them up yourselves. Putting business critical/private code into a public RCS/distribution hub is not always a good plan. Any python library with an standard setuptools install.py can be made into a source package by 'python setup.py sdist'. If you place all the required packages in a internal web accessible location, you can then use pip to discover and install packages from there directly, as though it were PyPi. Check out the pip flags --index-url, --extra-index-url and --find-links, which can be inserted into the pip requirements file. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
