Re: setup.py for project?

The choice depends on your requirements.

The code for djangoproject.com doesn't have a setup.py because we pull the code directly from git to "install" it on server. This makes deploying incremental changes easy as we just run Ansible which pulls the latest changes. We don't have the notion of "versions" or "release branches" for this code.

In a previous job, my team used Jenkins to create source distributions for each release and then installed them on our production servers. This made rolling back easier as we could simply install the previous version instead of reverting all commits for that version.

On Wednesday, April 1, 2015 at 4:48:26 AM UTC-4, guettli wrote:

Using a setup.py for reusable apps makes sense. This way you can
share the code via a pypiserver.

Our projects are very small. They don't have models, only config. With "project" I mean
the small (in our case) git repo which holds settings.py urls.py.

But does a setup.py make sense for the project?

How do you manage your projects (not apps)?

Regards,
   Thomas Güttler


--
Thomas Güttler
http://thomas-guettler.de/

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9322f8a3-a4f8-4e98-a065-34c3cda40555%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.