Opened 16 years ago
Closed 16 years ago
#7476 closed (invalid)
Decoupling URLconfs does NOT inherit imports
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | decoupling | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the docs, it isn't immediately transparant whether or not import statements such as "from django.conf.urls.defaults import *" are inherited by app-specific urls.py files. This may just be an issue for me because I'm just familiarizing myself with Python, but it seems like this could be useful information to include.
Change History (1)
comment:1 by , 16 years ago
| milestone: | 1.0 alpha |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I am not sure what this reporting exactly.
from django.conf.urls.defaults import *just imports some functions to use in the urls.py module. There is no inheritance going on here.includeis typically used to chain together urls from project to apps. Please defer to posting on django-users mailing list or asking in #django on freenode about any usage questions.