Jason F. McBrayer wrote: > Hi. I've more-or-less finished a django app that might be useful to > other people <snip, snip> > I'd like to package this for other people in a way that is as convenient > for them as possible, while not requiring too much work from me. So, > what do people expect from a third-party django app by way of packaging?
The Python world is slowly catching on to using Python "eggs" and the "cheeseshop" (gosh, I hate that name-- I'll henceforth only call it "The Shop".) "eggs" and "The Shop" are to Python as "packages" and "CPAN" are to Perl and "gems" and "rubyforge.org" are to Ruby. However, The Shop, CPAN, and rubyforge.org all look like they are meant for application-agnostic, but language-specific libraries or applications. For example, it looks like you can install Ruby on Rails as a ruby gem... but not a web-app written using ruby on rails. I wonder if the Python "Shopkeepers" would allow Django-specific apps to live in The Shop. If so, you have your answer: package your app as an egg (http://peak.telecommunity.com/DevCenter/PythonEggs) and submit it to cheeseshop.python.org. However, if you look at the Django subversion repository... it looks like you may already have your answer: http://code.djangoproject.com/browser/django/trunk/django/contrib If I was a betting man... I'd bet that the core Django developers expect community-built "ready to use" Django apps like yours will someday live in that 'contrib' folder on the code.djangoproject.com website. I think this thread should kick start the discussion with the Django devs about what can be uploaded to django/contrib... who gets access, resolving licensing issues, etc... If the Django devs don't/won't let you upload your code directly to the project's contrib folder anytime soon... With no other permissions from anyone, you could write a python "egg" today that will install your app to the django/contrib folder of a user's Django installation. Your installer script should look for where the Django library has been installed, and then save your app in django/contrib. Simply host your "egg" on your website for now, and edit the Django project wiki with a link to your file (http://code.djangoproject.com/wiki). Hope this helps! And I hope the core Django devs add their opinions on this topic. Django-all-the-way-ly yours, Jason Huggins
