Am 10.09.2008 um 18:20 schrieb mrts:

> If setuptools remains the recommended way of packaging apps (I don't
> necessarily oppose this, but I'd like to hear other opinions; what I
> don't like is littering CheeseShop with stuff that is unusable in
> general Python context), at least a fixed policy is needed:
> * designate a global namespace where all apps should live (e.g.
> django.apps.mycompany.fooapp or just django.apps.fooapp)
> * find a way for avoiding name collisions there (mycompany would deal
> with that)
> * document all the above and the steps and requirements for creating
> and publishing a reusable app.

Although this is a shameless plug, I'd like to point to a small helper  
app that is able to find resuable Django apps that are packaged as egg  
files. It's independent from the PYTHONPATH and hooks into the  
INSTALLED_APPS setting to automatically find every Django app that has  
a so called entry point, a pretty nice feature of setuptools to find  
components/plugins/pluggables [1]. It also works well with virtualenv.

For more information head over to http://code.google.com/p/django-reusableapps/ 
  and start making eggs.

Cheers,
Jannis


1: 
http://peak.telecommunity.com/DevCenter/setuptools#dynamic-discovery-of-services-and-plugins

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to