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 lemburg
Recipients belopolsky, elixir, ezio.melotti, gvanrossum, lemburg, r.david.murray, skip.montanaro, terry.reedy, tim.peters, vstinner
Date 2013-11-05.21:32:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On 05.11.2013 21:31, STINNER Victor wrote:
> 2013/11/5 Alexander Belopolsky <>:
>> +1 on adding an option to isoformat().  We already have an optional <sep> argument, so the symmetry with __str__ is not complete.  To make this option more useful, rather than implementing always_emit_microseconds=False flag, I would add a keyword argument 'precision' that would take ('hour'|'minute'|'second'|millisecond'|'microsecond') value.
> Hour precision is not part of the ISO 8601 standard.
> "resolution" is maybe a better name for the new parameter than "precision":
> The new parameter should be added to datetime.datetime.isoformat() but
> also datetime.time.isoformat().

Since this ticket is about being able to remove the seconds fraction
part, I think it's better to use a name that is not already overloaded
with other meanings, e.g. show_us=False or show_microseconds=False.

BTW: Have you thought about the rounding/truncation issues
associated with not showing microseconds ?

A safe bet is truncation, but this can lead to inaccuracies of
up to a second. Rounding is difficult, since it can lead to
a "60" second value showing up for e.g. 11:00:59.95 seconds,
or the need to return "12:00:00" for 11:59:59.95.
Date User Action Args
2013-11-05 21:32:18lemburgsetrecipients: + lemburg, gvanrossum, tim.peters, skip.montanaro, terry.reedy, belopolsky, vstinner, ezio.melotti, r.david.murray, elixir
2013-11-05 21:32:18lemburglinkissue19475 messages
2013-11-05 21:32:18lemburgcreate