About managing dependencies in a collaborative development team and good practices.
Santiago Basulto
some time ago with a couple of friends started a project with Django.
We are really getting into it now, and have made several progress in
the last 3 months. But, as the code starts to grow up, everything
start to get complicated.
Right now we have our project hosted on Bitbucket, and is simple to
set the enviroment to develop. Just clone the repo, syncdb, run a
script that install some fixtures, and runserver.
But, we started to use some externa apps, and add extra code, and it
started to look like a mess. Furthermore, we are 3 guys coding, it
starts to get complicated to all have the dependencies right.
After taking a look how pinax handle it, it seems a good option to
make use of PIP for the external apps, and create virtual envs.
First question then: Is that good? To use PIP with the external apps?
Will it be easy to deploy it?
Second question: What about our own apps? Should i let them live in
the project root directory? Should i try to pack them as "egg"
packages?
Finally: Do you have any good practice to tell me? Experience is
really needed!!
Thank you all!
PD: I have no much experience with Python, i'm a Java guy, and don't
think you like Maven ;)
Sébastien Billion
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
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Tom Evans
<sebastie...@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
Javier Guerra Giraldez
<sebastie...@gmail.com> wrote:
> 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.
i do exactly that. just a tip: to create and maintain the pip
requirements file do:
pip freeze > piprequirementsfile.txt
--
Javier
Shawn Milochik
>
> i do exactly that. just a tip: to create and maintain the pip
> requirements file do:
>
> pip freeze> piprequirementsfile.txt
>
+1
And it's checked into version control.
Shawn
Tom Evans
How else would one do Software Change Management? :)
Cheers
Tom
Santiago Basulto
I'm unsing virtualenvs and Pip. Seems great, is really easy that way.
What about deployment? Will it be simple? Or should i care about the
specific webserver?
Thanks!
Javier Guerra Giraldez
<santiago...@gmail.com> wrote:
> I'm unsing virtualenvs and Pip. Seems great, is really easy that way.
>
> What about deployment? Will it be simple? Or should i care about the
> specific webserver?
on deployment there should be a 'real' webserver (as opposed to the
development server) and probably some wsgi server, database, cache,
queues, whatever your project needs.
besides that 'platform' needs, you also have the webapp itself: your
project and all the python dependencies (django, and extra apps like
South, celery, tagging, etc.) for this, it's (almost) the same as for
development: create a virtualenv, pull from repository, and
pip-install all dependencies.
the main difference is that instead of you running the dev-server, the
infrastructure (including your wsgi server) will execute your app.
exactly how that's done is different for each deployment architecture.
--
Javier
