> I've not been following this thread at all, so apologies if this has > been brought up already. No, but unclear if it's relevant. > 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. Sure. So the interface may be different. The main argument (that you shouldn't be using t.year() to format dates) remains the same. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4