Hey Etienne, Sorry for this late answer, I'm now back at the game.. > > Egg files are great. We could easy_install them, assuming the user > or developer is already using setuptools.
Indeed - eggs will be in some way included in the next Python versions, if it is setuptools or as part of distutils. The fact remains, having a distributable format is the way to go if we don't want to collapse of the diversity of Django apps. > Agreed. In order to distribute reusable django apps, there should be > at least a common package namespace where all theses packages would > get > installed. I've thought the namespace "apps" would be a good > starting point for this. Definitely, "apps" is semantically and technically correct. > Again, I really like the idea to use setuptools and eggs for > distribution > of django apps/packages. However, Im less sure about adding anything > special inside a app for specifying metadata. Why not just use a > regular > setup.py script for distributing a standalone app ? Well, good point. One answer is the easy manipulation of the metadata by the user. Changing the setup.py could lead to unsuccessful packaging. That's why I moved it to the new metaphorical construct of a "release.py" within the application directory. The other reason is the the "Release" API I implemented in django.utils.package which gives the user the chance to manipulate a application release directly. Think of a Trac plugin or a Paste wrapper for example, using this information. > +1 for djangoapps.org and for using a common package namespace > for reusable django apps. [apps] > > Also, the freebsd ports collection is a great example of a well- > managed > collection of reusable apps. We should use this more for > inspiration.. :) Good idea, thanks for the tip! Jannis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
