Changes between Initial Version and Version 3 of Ticket #33387


Ignore:
Timestamp:
Dec 31, 2021, 9:23:48 AM (3 years ago)
Author:
אורי
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33387

    • Property Summary Separate between words in Django commands → Separate between words in Django commands and methods
    • Property Resolution → wontfix
    • Property Status new → closed
    • Property Type Uncategorized → Cleanup/optimization

  • Ticket #33387 – Description

    initial v3  
    55> Variable names follow the same convention as function names.
    66
    7 I think Django commands should follow the same logic, and separate words by underscores (`make_migrations`, `make_messages`, `change_password` and `create_super_user`, `remove_stale_content_types`). I suggest that you add the new spelling while keeping the old spelling working, or maybe deprecate the old spelling but for at least 3 Django releases, so they will still work. But according to PEP 8 I think words should be separated by underscores.
     7I think Django commands should follow the same logic, and separate words by underscores (`make_migrations`, `make_messages`, `change_password`, `create_super_user`, `remove_stale_content_types`). I suggest that you add the new spelling while keeping the old spelling working, or maybe deprecate the old spelling but for at least 3 Django releases, so they will still work. But according to PEP 8 I think words should be separated by underscores.
    88
    99This 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.
Back to Top