homepage

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, brian.curtin, catherine, cvrebert, docs@python
Date 2012年08月27日.10:20:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346062845.75.0.351658753903.issue9650@psf.upfronthosting.co.za>
In-reply-to
Content
I would like to add my +1 to this issue. I suggest adding something like this:
"""
Commonly used format codes:
%Y	Year with century as a decimal number.
%m	Month as a decimal number [01,12].
%d	Day of the month as a decimal number [01,31].
%H	Hour (24-hour clock) as a decimal number [00,23].
%M	Minute as a decimal number [00,59].
%S	Second as a decimal number [00,61].
%z	Time zone offset from UTC.
%a	Locale’s abbreviated weekday name.
%A	Locale’s full weekday name.
%b	Locale’s abbreviated month name.
%B	Locale’s full month name.
%c	Locale’s appropriate date and time representation.
Other codes may be available on your platform. See documentation for the C library strftime function.
"""
This is a subjective selection in a subjective order of importance, so some bikesheding is welcome. My choice was motivated by the assumption that most commonly used are the codes required to form RFC 3339 timestamps. I deliberately omitted deprecated %y code and the %Z code that produces non-standardized TZ names. I can be persuaded to add 12 hour clock codes.
History
Date User Action Args
2012年08月27日 10:20:45belopolskysetrecipients: + belopolsky, brian.curtin, cvrebert, docs@python, catherine
2012年08月27日 10:20:45belopolskysetmessageid: <1346062845.75.0.351658753903.issue9650@psf.upfronthosting.co.za>
2012年08月27日 10:20:45belopolskylinkissue9650 messages
2012年08月27日 10:20:44belopolskycreate

AltStyle によって変換されたページ (->オリジナル) /