[Python-Dev] Re: proposal: add basic time type to the standard library
Barry A. Warsaw
barry@zope.com
Tue, 26 Feb 2002 17:48:24 -0500
Tue, 26 Feb 2002 17:48:24 -0500
- Previous message: [Python-Dev] Re: proposal: add basic time type to the standard library
- Next message: [Python-Dev] Re: proposal: add basic time type to the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>>>>> "GvR" == Guido van Rossum <guido@python.org> writes: >> The localization context should not (always) be taken from the >> user environment. In systems like web-based services, the >> context will instead be relative to the person/entity making >> the remote request, so we have to be able to explicitly specify >> the localization context, or at least query, modify, and >> restore some global context. GvR> Sure. So the interface may be different. The main argument GvR> (that you shouldn't be using t.year() to format dates) GvR> remains the same. Doesn't Java have separate formatting objects? You decide which format object you need based on the localication context, then you pass in the timestamp/date/money/whatever thingie and the format object knowws how to render that data representation in the appropriate localization. makes-sense-to-me-ly y'rs, -Barry
- Previous message: [Python-Dev] Re: proposal: add basic time type to the standard library
- Next message: [Python-Dev] Re: proposal: add basic time type to the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]