search

liuyang1520 / django-command-extensions

Automatically exported from code.google.com/p/django-command-extensions
MIT License
0 stars 0 forks source link

Extension "bundling" #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It's the Ghost of Namespaces Yet To Be, again.  ;-)

Not that I don't love all django command extensions dearly, but many of my
projects don't need all of them at once.  Other users may find their own
personal reasons for wanting to cherry-pick extensions, so I'd like to
suggest a compromise:

'django_extensions' in INSTALLED_APPS includes all jobs commands (hooray,
no backwards-incompatible changes like *other* issues I bring up)

'django_extensions.jobs' in INSTALLED_APPS would include only create_jobs,
runjob, and runjobs (plus maybe runscript, if you swing that way)

...etc.

Thoughts?
Jason

p.s. I know django_extensions.jobs won't do for technical reasons.

Original issue reported on code.google.com by jbalo...@gmail.com on 6 Aug 2008 at 2:46

GoogleCodeExporter commented 8 years ago 
will that work ?

i would think that django will then look for a
django_extensions.jobs.management.commands type of structure.

would like it if it would work though, might is be specifying things in
INSTALLED_APPS or having our own knob in settings.py for it.

Original comment by v.oostv...@gmail.com on 6 Aug 2008 at 6:32

GoogleCodeExporter commented 8 years ago 
the only way i know atm to make this work is to break up django_extensions 
inside an
app per command/feature. that way you could do "django_extensions.*" in
INSTALLED_APPS for everything and install things on a per app basis.

_but_ and this is major but :) i feel that breaking it up in so many little 
parts
will do us more harm then good.

feel free to open this ticket at a later time when somebody has a 'better' way 
to do
this. (i would prefer a DJANGO_EXTENSIONS_INCLUDE/EXCLUDE kind of knob in 
settings.py)

Original comment by v.oostv...@gmail.com on 6 Sep 2008 at 3:45