Changes between Initial Version and Version 2 of Ticket #13512


Ignore:
Timestamp:
May 10, 2010, 7:52:06 AM (15 years ago)
Author:
Karen Tracey
Comment:

Sounds like (though details of the traceback have changed in the interim): ​http://code.djangoproject.com/ticket/11696#comment:12. Prior to the introduction of module_has_submodule, things found in INSTALLED_APPS that did not have a __path__ were just ignored. The check was originally put in for "odd things" like eggs (though it's not necessary for eggs); the original person who hit a problem which caused the check to be added actually had a completely unnecessary non-app listed in INSTALLED_APPS. If there's a valid reason for having things in INSTALLED_APPS that don't have a __path__ then we can probably deal with it in module_has_submodule, but I haven't heard that reason yet. The one person who originally ran into the issue when the __path__ check was put in acknowledged it was caused by an error in their INSTALLED_APPS.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13512

    • Property Resolution → worksforme
    • Property Status new → closed

  • Ticket #13512 – Description

    initial v2  
     1{{{
    12Traceback (most recent call last):
    23  File "src/project/manage.py", line 18, in <module>
    … …  
    3738    for entry in package.__path__:  # No __path__, then not a package.
    3839AttributeError: 'module' object has no attribute '__path__'
     40}}}
Back to Top