[issue2782] datetime/date strftime() method and time.strftime() inconsistency

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: Fixed in trunk (2.6) r63887. -- assignee: gregory.p.smith -> resolution: -> fixed status: open -> closed versions: -Python 2.6 ___ Python tracker <[EMAIL PROTECTED]>

[issue2782] datetime/date strftime() method and time.strftime() inconsistency

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: Yes, sounds like a bug. I'll fix it. But should time.strftime allow a unicode format string as input in the first place? For backwards compatibility I'd say yes. But.. Sane output can not be guaranteed from time.strftime when given a uni

[issue2782] datetime/date strftime() method and time.strftime() inconsistency

Changes by Alexandr Zamaraev <[EMAIL PROTECTED]>: -- nosy: +shura_zam __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubs

[issue2782] datetime/date strftime() method and time.strftime() inconsistency

Changes by broadus jones <[EMAIL PROTECTED]>: -- nosy: +sbj3 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: h

[issue2782] datetime/date strftime() method and time.strftime() inconsistency

New submission from Andrii V. Mishkovskyi <[EMAIL PROTECTED]>: datetime and date strftime() method does additional check on input format, thus being completely different from time's module time.strftime() method behavior. There are two ways to fix this: 1. Add an explicit note about this behavior