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 catherine
Recipients catherine
Date 2010-08-20.15:49:37
SpamBayes Score 7.284617e-08
Marked as misclassified No
Message-id <1282319380.5.0.724924373031.issue9650@psf.upfronthosting.co.za>
In-reply-to
Content
Is there any reason not to include the strftime formatting codes in the docstrings of time.strftime and time.strptime? 

>>> print time.strftime.__doc__
strftime(format[, tuple]) -> string

Convert a time tuple to a string according to a format specification.
See the library reference manual for formatting codes. When the time tuple is not present, current time as returned by localtime() is used.


Sending users to look up such a basic, frequently-used, hard-to-remember set of codes in the docs every single time seems unfriendly.  Even a tightly abbreviated list would be very convenient.
History
Date User Action Args
2010-08-20 15:49:41catherinesetrecipients: + catherine
2010-08-20 15:49:40catherinesetmessageid: <1282319380.5.0.724924373031.issue9650@psf.upfronthosting.co.za>
2010-08-20 15:49:38catherinelinkissue9650 messages
2010-08-20 15:49:37catherinecreate