Opened 5 years ago
Closed 5 years ago
#31127 closed Cleanup/optimization (invalid)
Django should warn (or throw an error) when creating a new app called 'app'.
Reported by: | Bruce | Owned by: | nobody |
---|---|---|---|
Component: | Core (Management commands) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I created an app called 'app' in my project using the management command 'startapp'.
I think this should throw an error or warn the user, as it brings some implications:
For example, the AppConfig of the app called 'app' is called AppConfig by default.
This breaks the AppConfig, as it can't be called that.
(I noticed this when debugging why my signals didn't work)
I would be willing to work on this.
Change History (1)
comment:1 by , 5 years ago
Easy pickings: | unset |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Summary: | Django should warn (or throw an error) when creating a new app called 'app' → Django should warn (or throw an error) when creating a new app called 'app'. |
UI/UX: | unset |
Version: | 3.0 → master |
Note:
See TracTickets
for help on using tickets.
App called
app
works perfectly fine for me (also with signals).class AppConfig(AppConfig)
will locally redefine importeddjango.apps.AppConfig
, so it works properly.