[M.-A. Lemburg] >> ... >> It's also possible (easy) to create tzinfo subclasses that model >> only EST, or only EDT, but they seem less useful in real apps. [M.-A. Lemburg] > In that case you should follow the standard way of using > the name of the locale to define your timetz subclasses, > e.g. EasternUS, CentralUS, etc. I don't care what people call their classes. Remember that datetime supplies no tzinfo subclasses. If a user wants some, they have to supply their own, and can use any naming convention they like. Eastern was just an example (not part of the 2.3 distribution).
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