Opened 7 years ago

Closed 7 years ago

#7476 closed (invalid)

Decoupling URLconfs does NOT inherit imports

Reported by: jesse.b.obrien@… Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: decoupling
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


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 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 Changed 7 years ago by brosner

  • milestone 1.0 alpha deleted
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

I am not sure what this reporting exactly. from django.conf.urls.defaults import * just imports some functions to use in the module. There is no inheritance going on here. include is 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.

Note: See TracTickets for help on using tickets.
Back to Top