#7442: docs about decoupling urls doesn't decouple all the way
------------------------------------+---------------------------------------
Reporter: siva_ | Owner: nobody
Status: closed | Milestone:
Component: Documentation | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by newbie):
At the risk of arguing endlessly, I respectfully agree with my fellow
Django initiate. If I understand the significance of apps and projects
properly, this is not only not decoupled, but it is doubly coupled. If
the maintainer of a project has to modify project-level settings to
include someone else's application, that's understood, although the fewer
modifications necessary, the better. If the maintainer of a project has
to modify both the project and the application, that's not so desirable.
Is there some way that patterns() can be made to reference the invoking
module without having to identify it by name?
--
Ticket URL: <http://code.djangoproject.com/ticket/7442#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
