Django makes assumptions about the filesystem layout of python packages here and there, and will silently skip any app which does not meet Django's assumptions without raise up any warning. I had been bitten by this many times before I learned that Django and Django apps should never be packaged as zip-archived eggs.
IMHO, all these problems can be solved by adding support for PEP 302 importers. And I found that there are three different kinds of problems. 1. find submodules before importing the package: finding management commands 2. find submodules after importing the package: finding template tags and listing available database backends 3. find resource files after importing the package: template files, static files, fixtures and translation files Finding template tags in zip-archived eggs has already been solved by #13334. and I have been working on solve remaining problems in the past few months, and have all but 2 related regression tests passed, and code is now available on Github: https://github.com/bhuztez/django/compare/master...pep-302 How many tickets should I open on trac? a single ticket for all, or one ticket for each problem, or one ticket for each related parts of code which would be six or more? Any ideas? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
