Paul Ganssle

I think that `isoparse` is intended to be strict, but the precise form of the strictness is not guaranteed because the spec is limited or ambiguous in some ways, and...

This is indeed out of spec, so we can at least fix `parser.isoparse` allowing the hours or minutes component to be a single digit. I've opened PR #1077.

I would like to suggest that this is *probably* a bad idea at least if the motivation is to create a recommended build tool to replace `setup.py sdist bdist_wheel`. I...

> I'd rather we did that by delegating _all_ of the build processes to a separate library that could be shared among different tools. The `pep517` library is probably where...

I think I originally planned to do this but it made the implementation a bit more complicated and maybe all the pieces to do it weren't in place / stable...

@serhiy-storchaka Are you sure you got the bpo issue right? Looks unrelated to me.

I basically agree with this — this is one of the reasons I structured the zoneinfo module the way I did rather than mimicking the pattern in datetime. I believe...

> bout \_strptime, I see that the time.strptime() imports internally the \_strptime module. Ah, sorry, my remark about including `_strptime` was off the cuff — I thought it was only...

As for deciding between moving to `datetime/` and moving to `_pydatetime`, I think we should send an e-mail to Python-Dev about it to get a wider perspective, because the import...

I don't think we need to close this just because you won't be fixing it yourself. It is still a valid issue