On Sat, 2007-09-22 at 11:52 +0800, Russell Keith-Magee wrote:
> On 9/22/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> >
> > I have a couple of reservations about the version of app commands that
> > got committed and just wanted to bring them up here.
> ...
> > I'm worried that we're setting ourselves up for two things:
> > 1. Name collisions.
> > 2. Command confusion.
> 
> I can see what you're talking about here, but IMHO it's a much smaller
> potential problem than you think. Consider - we install applications
> using a single keyword identifier (the app name), and while there are
> occasional discussions about how to allow for deploying two
> applications with the same name, it isn't a use case that is very
> common.

Right. But now we have the problem of apps overriding core commands. Do
we want that as a possibility? It opens a can of worms in terms of being
able to figure out what the heck is going on. "I ran ./manage.py syncdb
and it deleted my whole database. What happened?"

> Adding user-space commands is something that only a subset of
> applications will need to do. As a result, there is even less
> potential for clashes here than there is in application space.
> Complicating the basic interface for the invocation of commands to
> account for clashes that aren't likely seems like overkill to me.

I don't follow this logic. If even one app provides several commands,
the potential for conflict between it and another app's commands exists.

> However, I agree that the help output could be improved to avoid any
> potential confusion; ./manage.py help could organize user-defined
> commands separately, and ./manage.py help foobar could display the
> application that provided the command. Patches welcome :-)

See the original patch for the first part of this. :-)

Todd


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
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