The use case for namespace packages is the ability to fragment portions of a single package across multiple disparate locations on the filesystem. And, potentially, to install or selectively enable/disable access to only certain sub-portions of the package by choosing which parts are present or by adding/removing their locations in the import path.
Way way back in the day template tag libraries used to do a hack that simulated this, where Django would see a "templatetags" directory in your app and magically make it be importable from under "django.templatetags" instead. That was one of the last pieces of the original "magic" to be removed. There's no reason to create implicit namespace packages for management commands unless we want to move back to that sort of magical "lives over *there* but imports as if it's actually over *here*" behavior, and I'm pretty sure we don't want to do that. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAL13Cg_4Ea0%3DAe2zzgHw63JAGDRXH3T40UQ27Nd2OQHy5HhQQg%40mail.gmail.com.
