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 belopolsky
Recipients belopolsky, elixir, ezio.melotti, gvanrossum, r.david.murray, skip.montanaro, terry.reedy, tim.peters, vstinner
Date 2013-11-05.21:24:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383686687.39.0.777489179079.issue19475@psf.upfronthosting.co.za>
In-reply-to
Content
+1 on all Victor's points.

I like 'resolution' because this is the term that datetime module uses already:

>>> from datetime import *
>>> datetime.resolution
datetime.timedelta(0, 0, 1)

There is a slight chance of confusion stemming from the fact that datetime.resolution is timedelta, but proposed parameter is a string.

I believe ISO 8601 uses the word "accuracy" to describe this kind of format variations.  I am leaning towards "resolution", but would like to hear from others.  Here are the candidates:

1. resolution
2. accuracy
3. precision

(Note that "accuracy" is the shortest but "resolution" is the most correct.)
History
Date User Action Args
2013-11-05 21:24:47belopolskysetrecipients: + belopolsky, gvanrossum, tim.peters, skip.montanaro, terry.reedy, vstinner, ezio.melotti, r.david.murray, elixir
2013-11-05 21:24:47belopolskysetmessageid: <1383686687.39.0.777489179079.issue19475@psf.upfronthosting.co.za>
2013-11-05 21:24:47belopolskylinkissue19475 messages
2013-11-05 21:24:47belopolskycreate