This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: datetime class names should obey PEP 8 CapWords convention
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.1
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: gvanrossum, jess.austin
Priority: normal Keywords: patch

Created on 2009-03-21 05:02 by jess.austin, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
pending_dep.diff jess.austin, 2009-03-21 05:02 unified diff against branches/py3k
Messages (2)
msg83921 - (view) Author: Jess Austin (jess.austin) Date: 2009-03-21 05:02
Class names that comply with the CapWords naming convention described in
PEP 8 ( are preferred. See the
recent discussion that included the BDFL's recommendations at

Per those recommendations, the attached patch updates every class to
expose a CapWords name to python:

datetime.timedelta  -->  datetime.TimeDelta       -->  datetime.Date
datetime.tzinfo     -->  datetime.TZInfo
datetime.time       -->  datetime.Time
datetime.datetime   -->  datetime.DateTime

In addition, the old lowercase names are reproduced as derived classes,
the methods of which throw PendingDeprecationWarning, and the docstrings
of which advise using the new CapWords class names. The
unit test is updated to check for proper functionality and for the
presence of the pending deprecation warnings. (This patch relies on the
previously-submitted refactoring patch attached to Issue 5520, Various other tests and support files
are updated to use the new CapWords class names.

The current patch still fails one test in, due to
previously-existing Issue 5516,

This patch includes no documentation updates.
msg84109 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2009-03-24 20:14
Please don't do this. We need stable APIs. Trying to switch the entire
community to use CapWord APIs for something as commonly used as datetime
sounds like wasting a lot of cycles with no reason except the mythical
"PEP 8 conformance". As I said, it's a pity we didn't change this at the
3.0 point, but I think going forward we should try to be more committed
to slow change. Additions of new functionality are of course fine. But
renamings (even if the old names remain available) are just noise.
Date User Action Args
2022-04-11 14:56:46adminsetgithub: 49780
2009-03-24 20:14:30gvanrossumsetstatus: open -> closed

nosy: + gvanrossum
messages: + msg84109

resolution: rejected
2009-03-21 05:02:37jess.austincreate