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 techtonik
Recipients ajaksu2, belopolsky, daniel.urban, eric.araujo, l0nwlf, mihaic, poolie, r.david.murray, techtonik
Date 2012-06-14.13:36:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPkN8xJKgu11o790WbmDGiTcDXp3J7z0KcLd-Tt=4k_Y6H7xdw@mail.gmail.com>
In-reply-to <1279061543.77.0.750672834209.issue7584@psf.upfronthosting.co.za>
Content
On Wed, Jul 14, 2010 at 1:52 AM, Alexander Belopolsky
<report@bugs.python.org> wrote:
> I am still -1 on adding specialized formatting methods to the datetime class.  I think this should be done in specialized modules.

No problem - add "formats" module and I'll be happy.

>On the other hand, datetime module should provide facilities to easily implement such methods and there does not seem to be a good solution for implementing locale independent formats.  I would like to consider the idea of adding datetime.cstrftime() which provides formatting equivalent to datetime.strftime() in "C" locale.  Another feature that will be needed to implement rfcformat, would be a GNU date style "%:z" code.

If there is no best solution then the best out worse solutions is much
much better - provided that an appropriate explanation is available
for the users.
History
Date User Action Args
2012-06-14 13:36:04techtoniksetrecipients: + techtonik, belopolsky, ajaksu2, eric.araujo, r.david.murray, daniel.urban, l0nwlf, mihaic, poolie
2012-06-14 13:36:04techtoniklinkissue7584 messages
2012-06-14 13:36:03techtonikcreate