[Lie Ryan] > How about having a country code field, e.g. en-us would format according > to US locale, in to India, ch to China, etc... that way the format > string would become very simple (although the lib maintainer would need > to know customs from all over the world). Then have a special country > code that is a placeholder for whatever the locale the machine is set to. Am moving the discussion to the python-ideas list (at Guido's request). My proposal is strictly limited to the builtin, non-locale dependent formatting. Improvements to the locale module are probably as subject for another day. Raymond
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