#33387: Separate between words in Django commands and methods
-------------------------------------+-------------------------------------
     Reporter:  אורי                 |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Core (Management     |                  Version:  dev
  commands)                          |
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * type:  Uncategorized => Cleanup/optimization
 * resolution:   => wontfix


Comment:

 > I checked the list of [https://docs.djangoproject.com/en/4.0/ref/django-
 admin/ Django commands], and a long time ago I noticed that many of them
 contain two or even three words but they are not separated. For example
 `makemigrations`, `makemessages`, `changepassword` and `createsuperuser`.
 Although I found commands with separated words such as
 `remove_stale_contenttypes` (which I was not aware of until right now). I
 checked [https://www.python.org/dev/peps/pep-0008/#function-and-variable-
 names PEP 8] and there it is written:

 Thanks for this ticket, however I don't think it's worth changing just to
 follow PEP 8 it's really disruptive. In the case of such changes, it's
 crucial to have a strong consensus and clear significant benefits.

 > This is also relevant to `TestCase` methods such as `setUp` and
 `tearDownClass`. Although there I assume Django inherits them from Python
 the language, and maybe the changes should be done also there.

 The `unittest` unit testing framework was originally inspired by JUnit
 that's why it has camel-cased methods.

 You can raise the idea on the DevelopersMailingList or the python-ideas
 list (it was probably already raised) to reach a wider audience and see
 what other think, however I don't think there would be consensus to change
 that.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33387#comment:2>
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/069.6c11c7ce4228bb01bd817de6f5e4438f%40djangoproject.com.

Reply via email to