|Reported by:||James Bennett||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Description (last modified by )
packages argument only accepts modules which are either
django.conf or which are also in
INSTALLED_APPS. But there are two issues with this:
- The documentation for the view hides this a bit, and can create the impression that the restriction only applies to a
packagesargument passed through the URL.
- The view itself does not give you any warning if you're violating this restriction; it just silently discards anything in
packagesthat doesn't meet the requirements.
At the very least, the documentation should be more up-front that this requirement always applies no matter how you're passing
packages to the view. Possibly as a bonus, the view should warn that it's discarding any packages that don't conform to the requirements, to aid in debugging.
Change History (4)
comment:1 Changed 4 years ago by
|Component:||Documentation → Internationalization|
|Triage Stage:||Unreviewed → Accepted|