Message 151388 - Python tracker

➜

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	eric.araujo
Recipients	belopolsky, brett.cannon, docs@python, eric.araujo, eric.smith, flox, r.david.murray
Date	2012-01-16.16:39:36
SpamBayes Score	0.0045102104
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
IMO, now that two official releases of Python 3 have shipped with this behavior (3.1 and 3.2), it is too late to think about changing what datetime.__format__ does, and we should merely document that it is the same as strftime.

IMO, now that two official releases of Python 3 have shipped with this behavior (3.1 and 3.2), it is too late to think about changing what datetime.__format__ does, and we should merely document that it is the same as strftime.

History
Date	User	Action	Args
2012-01-16 16:39:37	eric.araujo	set	recipients: + eric.araujo, brett.cannon, belopolsky, eric.smith, r.david.murray, flox, docs@python
2012-01-16 16:39:37	eric.araujo	set	messageid: <[email protected]>
2012-01-16 16:39:36	eric.araujo	link	issue8913 messages
2012-01-16 16:39:36	eric.araujo	create