Kevin Rasmussen added the comment:
Eric makes a pretty good point about how that ends up looking with days
included and backward compatibility.
Thanks everyone for humouring me and talking me through this one I'm going to
close the issue as "not a bug".
--
resolution: -&
Kevin Rasmussen added the comment:
Question:
Why should it be zeropadded to 2?
Answer:
Why wouldn't it be zeropadded to match the rest of the library?
Honestly it just seemed like an inconsistency with the rest of the datetime
module.
It caught me off guard when I went I tried to pull
Kevin Rasmussen added the comment:
Current behaviour:
```
# python
Python 3.9.1 (default, Dec 18 2020, 05:16:04)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> td
Change by Kevin Rasmussen :
--
keywords: +patch
pull_requests: +22908
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24075
___
Python tracker
<https://bugs.python.org/issu
New submission from Kevin Rasmussen :
It looks like hh should be zeropadded to 2 and isn't for timedelta.
--
messages: 384273
nosy: krasmussen
priority: normal
severity: normal
status: open
title: timedelta zeropadding hh
type: behavior
versions: Python 3.10
