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.

Author p-ganssle
Recipients Anthony Sottile, belopolsky, p-ganssle
Date 2020-07-09.19:06:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594321590.32.0.135345033902.issue41260@roundup.psfhosted.org>
In-reply-to
Content
I think a positional-only argument would be the best option if we could do it, but it would be a backwards-incompatible change and it's probably not worth the hassle.

If anyone is using the keyword argument, they're probably using `format=` rather than `fmt=`, since it's pretty rare for anyone to use the pure python version of datetime. PyPy uses it, but I think they tend to aim for consistency with the C API of CPython, and it seems like they already patch s/fmt/format/ themselves: https://foss.heptapod.net/pypy/pypy/-/blob/branch/default/lib_pypy/datetime.py#L781

If anyone wants to make a PR I think we can fix this for 3.10, though unfortunately because it is an API change it can't be backported. I think in typeshed they can safely change from `fmt` to `format` even today (which would almost certainly be more accurate to end user use cases).
History
Date User Action Args
2020-07-09 19:06:30p-gansslesetrecipients: + p-ganssle, belopolsky, Anthony Sottile
2020-07-09 19:06:30p-gansslesetmessageid: <1594321590.32.0.135345033902.issue41260@roundup.psfhosted.org>
2020-07-09 19:06:30p-gansslelinkissue41260 messages
2020-07-09 19:06:30p-gansslecreate