-----Original Message----- From: Python-ideas
On Behalf Of James Lu Sent: 03 February 2019 04:57 To: Steven D'Aprano Cc: python-ideas@python.org Subject: Re: [Python-ideas] Consistency in naming [was Re: ...ALL CAPS]
<snip>
I accept that datetime.datetime reads a bit funny and is a bit annoying. If we had the keys to the time machine and could go back a decade to version 3.0, or even further back to 1.5 or whenever the datetime module was first created, it would be nice to change it so that the class was DateTime. But changing it *now* is not free, it has real, serious costs which are probably greater than the benefit gained. Why can’t we put “now” as a property of the module itself, reccomend that, and formally deprecate but never actually remove datetime.datetime.now?
[Steve Barnes] Better yet why not also rename datetime.datetime to datetime.DateTime and include the line: datetime = DateTime. <snip>
A big reason why projects last as long as you say they last is that the maintainers get un-ambitious, they get used to relaxing in the language they know so well, they are no longer keen on change.
This kind of readability issue, datetime.now, is an example of what’s contributing to Python’s decline.
Bottom line: if someone submits a PR for this, will anyone merge it?
--
[Steve Barnes] Good Points