On 9/22/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > Yes, there _could_ be a clash of commands, and a user application > _could_ override a default Django command. However, I put it to you > that this is the 1% case, not the 99% case. Most applications won't be > registering commands, so there isn't a huge probability that a clash > will occur - even less of a probability than with applications. Only a > malicious application would try to register a command called 'syncdb', > and I think the Django community is savvy enough to spot those > applications and avoid them.
I don't think the likelihood is as low as you suggest. True, not all applications will register commands, but I imagine those that do will often register multiple commands. In addition, I think there is a higher likelihood that any two given commands will share the same name than any two given apps, especially if apps start to copy useful commands from other apps. Put those together, and I think that command name collisions could turn out to be more common than app name collisions after all. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
