On Wed, Sep 10, 2008 at 9:31 AM, mrts <[EMAIL PROTECTED]> wrote: > * create a central app index à la Cheeseshop
Doesn't the Cheese Shop already exist? > * create an automated system similar to easy_install for installing > apps from > o that central repository "easy_install django-registration" works fine for me right now. Why not encourage people to use standard Python practices for packaging and distribution? > o either globally to Python packages -- *but under django namespace! > * > o or locally into a concrete project Does anybody else actually do this? Last I checked, Pylons, TurboGears and Zope apps didn't install or need to be installed into framework-specific locations. Django applications are just Python modules, and that's a *strength* from where I sit. > * provide app dependency handling like setuptools does for > o python package dependencies (identical to setuptools 'depends') > o Django app dependencies (e.g. 'django_app_depends') Or just, you know, use setuptools. > * bundle the install tool either as a command for manage.py or a > separate utility in bin Or just, you know, install setuptools. > * create the solution so that it can be adopted by other projects by > clearly decoupling Django-specific functionality (i.e. engage more > brainpower and devs) Or just use the existing packaging and distribution tools Python already has. Have I made my point clear enough yet? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
