naming a template tag library the same as an app causes import problems
|Reported by:||akaihola||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The Django documentation warns about name clashes between custom tag libraries. However, there's no mention about the following problem:
If you have the same name for an app and a tag library, you can't import the app from any other tag libraries. Python first looks up the name among all tag libraries, finds the module there and tries to import that.
This behavior and the incompleteness of the documentation was confirmed by Eric Holscher and lericson on #django-dev a few minutes ago.