Opened 23 months ago
Closed 23 months ago
#34326 closed Cleanup/optimization (invalid)
Standardize case for commands
| Reported by: | Shiva Shane Ramdeen | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | Commands, Command Case |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Are there any plans to standardize the case of commands in django?
As an alternative the ability to automatically match snake_case to flatcase command names would be helpful.
Change History (3)
follow-up: 2 comment:1 by , 23 months ago
comment:2 by , 23 months ago
Core commands are not an issue. they are pretty consistent for the most part. The issue really is with django_extensions. Each project is consistent with either snake_case or flatcase but inter inter app commands feel inconsistent.
maybe it might be a good idea to investigate this type of change in the django_extensions repo instead, not sure.
Replying to Tim Graham:
It looks like there are two built-in commands that use underscores (snake case):
remove_stale_contenttypesandping_google. I never noticed the inconsistency, and I doubt it causes much confusion. Are you really struggling with it? Perhaps commands in third-party packages are affected?
comment:3 by , 23 months ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
django-extensions is a 3rd-party package. Please report it on their issue tracker.
It looks like there are two built-in commands that use underscores (snake case):
remove_stale_contenttypesandping_google. I never noticed the inconsistency, and I doubt it causes much confusion. Are you really struggling with it? Perhaps commands in third-party packages are affected?