#32382: Django 3.2 app config search prevents single-file apps
-------------------------------------+-------------------------------------
     Reporter:  Adam Johnson         |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Core (Other)         |                  Version:  3.2
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Adam Johnson:

Old description:

> My third party package django-read-only is implemented as a single file
> ([pre-3.1-support source](https://github.com/adamchainz/django-read-
> only/blob/e95530273fd75da34fd77b1625549ffd3840beaa/src/django_read_only.py)).
> With Django <3.2's `default_app_config`, it could point to its app config
> within the same module by defining `default_app_config`.
>
> Now the AppConfig logic *requires* an `apps` submodule, which means apps
> cannot be single-file modules but have to be packages.
>
> To work around this in django-read-only I made it into package, left all
> the logic in its `__init__.py`, and added a "dummy" `apps.py` that has
> only the line `from django_read_only import DjangoReadOnlyAppConfig`
> (moving the app config would complicate its implementation).
>
> Could we make the apps logic not search for an 'apps' submodule in the
> case of non-package modules, and instead check in the base module?

New description:

 My third party package django-read-only is implemented as a single file
 ([https://github.com/adamchainz/django-read-
 only/blob/e95530273fd75da34fd77b1625549ffd3840beaa/src/django_read_only.py
 pre-3.1-support source]). With Django <3.2's `default_app_config`, it
 could point to its app config within the same module by defining
 `default_app_config`.

 Now the AppConfig logic *requires* an `apps` submodule, which means apps
 cannot be single-file modules but have to be packages.

 To work around this in django-read-only I made it into package, left all
 the logic in its `__init__.py`, and added a "dummy" `apps.py` that has
 only the line `from django_read_only import DjangoReadOnlyAppConfig`
 (moving the app config would complicate its implementation).
 ([https://github.com/adamchainz/django-read-
 only/pull/37/commits/392056b4bbc1eb1ce25b159134e2ab114ca0cdcb commit ])

 Could we make the apps logic not search for an 'apps' submodule in the
 case of non-package modules, and instead check in the base module?

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32382#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.adc7fa0431cb154dadec1a8b03ffe248%40djangoproject.com.

Reply via email to