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 gvanrossum
Recipients gvanrossum, jess.austin
Date 2009-03-24.20:14:30
SpamBayes Score 3.3821057e-11
Marked as misclassified No
Message-id <1237925672.22.0.61136384924.issue5530@psf.upfronthosting.co.za>
In-reply-to
Content
Please don't do this. We need stable APIs. Trying to switch the entire
community to use CapWord APIs for something as commonly used as datetime
sounds like wasting a lot of cycles with no reason except the mythical
"PEP 8 conformance". As I said, it's a pity we didn't change this at the
3.0 point, but I think going forward we should try to be more committed
to slow change. Additions of new functionality are of course fine. But
renamings (even if the old names remain available) are just noise.
History
Date User Action Args
2009-03-24 20:14:32gvanrossumsetrecipients: + gvanrossum, jess.austin
2009-03-24 20:14:32gvanrossumsetmessageid: <1237925672.22.0.61136384924.issue5530@psf.upfronthosting.co.za>
2009-03-24 20:14:30gvanrossumlinkissue5530 messages
2009-03-24 20:14:30gvanrossumcreate