[issue40076] isoformat function drops microseconds part if its value is 000000

Paul Ganssle added the comment: > isoformat function does not conform to the ISO 8601 and drops microseconds > part if its value is 00. I'm not sure why you think that this does not conform to ISO 8601 - ISO 8601 is a sprawling beast of a spec and allows some crazy formats. Some

[issue40076] isoformat function drops microseconds part if its value is 000000

Change by Alexander Bolshakov : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue40076] isoformat function drops microseconds part if its value is 000000

Change by SilentGhost : -- nosy: +SilentGhost ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40076] isoformat function drops microseconds part if its value is 000000

Karthikeyan Singaravelan added the comment: Does timespec fulfill this use case to always return microseconds? https://docs.python.org/3/library/datetime.html#datetime.datetime.isoformat Return a string representing the date and time in ISO 8601 format: -MM-DDTHH:MM:SS.ff, if

[issue40076] isoformat function drops microseconds part if its value is 000000

Change by Karthikeyan Singaravelan : -- nosy: +belopolsky, p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue40076] isoformat function drops microseconds part if its value is 000000

New submission from Alexander Bolshakov : isoformat function does not conform to the ISO 8601 and drops microseconds part if its value is 00. The issue can be reproduced using the following code snippet: for i in range(1,1000): timestamp=datetime.datetime.utcnow().isoformat()