[issue22250] unittest lowercase methods

Serhiy Storchaka added the comment: https://www.python.org/dev/peps/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds -- ___ Python tracker ___

[issue22250] unittest lowercase methods

Rémi Lapeyre added the comment: See for example https://mail.python.org/archives/list/python-id...@python.org/thread/4HE2GFL27LGBSHGWOBDOOBPEULC52U4D/#RC3QWQUX6VP56K2WXSMRZ5IGNAUBXKRI -- nosy: +remi.lapeyre ___ Python tracker

[issue22250] unittest lowercase methods

Ram Rachum added the comment: I see it's been 6 years since the last comment here. I think it's important to revisit these kind of decisions once in a while. Maybe now the time is ripe for a change? We could do it backward compatibility with a long deprecation schedule. Ezio: You said this

[issue22250] unittest lowercase methods

New submission from Simon Zack: The python unittest module currently uses camel case. This feels rather inconsistent with the rest of the python library, which is in lower case and follows PEP8. Would it be a good idea to add lower-case aliases, and possibly deprecate the camel case methods

[issue22250] unittest lowercase methods

R. David Murray added the comment: We tried going down this path with the Threading module in the python3 transiontion, and it was a mess. I don't think we are going to do it for any other module. -- nosy: +r.david.murray ___ Python tracker

[issue22250] unittest lowercase methods

Serhiy Storchaka added the comment: assertlessequal looks non-readable and assert_less_equal is two characters longer. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22250

[issue22250] unittest lowercase methods

Ezio Melotti added the comment: This has been already proposed and rejected in the past. It's not something that is going to happen (at least until Python 4 or 5). -- nosy: +ezio.melotti resolution: - rejected stage: - resolved status: open - closed