[enhancement] Packing with distutils

[GoogleCodeExporter]

In order to use django-syncr in a requirements.txt file so that it can be
automatically installed into a virtualenv by pip, I needed to package it
with distutils.  To do this, I borrowed heavily from Django's own setup.py,
and I moved everything into a syncr folder to use as the syncr namespace. 
This is required for the setup.py to work correctly.

The diff I've generated looks huge because everything has been moved
around, but in reality the only change is that everything is under the
syncr/ directory now, and I've created a setup.py.  I'll be using a fork at
http://bitbucket.org/bkonkle/django-syncr/overview/ to house this
distutils-enabled version until you've had a chance to look this over and
make a decision on whether to move in this direction.  Thanks for such a
fantastic project, by the way!

Original issue reported on code.google.com by brandon....@gmail.com on 15 Jul 2009 at 3:39

Attachments:

• distutils-packaging.diff

[GoogleCodeExporter]

This is cool, I have been thinking about packaging for a while now. I will take 
a look at your patch, but I think 
this sounds like the way to go as far as packaging is concerned... 

Original comment by jesse.l...@gmail.com on 24 Jul 2009 at 12:49

• Changed state: Accepted
• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thanks!  Yeah, I've been diving into virtualenv and virtualenvwrapper lately, 
and
they makes things so much easier to work with.  I've been following Pinax's 
lead by
writing a script that creates and updates a bootstrap.py script which will set 
up the
environment automatically and then run pip to install all needed requirements.  
To
begin developing on a new computer, all I have to do is run the bootstrap 
script and
within minutes every requirement is in place and completely isolated from every 
other
project.  To deploy a new release to production, I can use fabric to wipe out 
the old
virtualenv within seconds and automatically build the new one with updated 
versions
of requirements.

Anyway, I'm rambling.  The bottom line is that every requirement needs to be 
packaged
with distutils or setuptools, so I've been packaging up everything I can find.  
:-)

Original comment by brandon....@gmail.com on 24 Jul 2009 at 1:53

[GoogleCodeExporter]

I should have gotten around to doing this a LONG time ago. Sorry for not 
getting to it. Yash implemented 
something similar to your patch (maybe he used this diff, I haven't talked to 
him about it) last month, so we're 
now using setup.py. I have been making some adjustments this morning but when 
I'm done, I'll probably wrap it 
all up in a zip/tar release. THANK YOU.

Original comment by jesse.l...@gmail.com on 5 Dec 2009 at 7:53

• Changed state: Started

[GoogleCodeExporter]

I've attached a setuptools based setup.py file. It fails installing 
django-syncr as dependency because the file 
download in http://code.google.com/p/django-syncr/ (version 0.41) have no 
setup.py.

If you can use a setuptools based setup.py instead a distutils based, the 
django-tagging dependency can be 
installed automatically with easy_install.

If you want a setuptools setup.py for your proyect, say me and I develop it ;-)

Original comment by lasizoi...@gmail.com on 25 Dec 2009 at 11:02

Attachments:

• setup.py