On Tue, Jul 28, 2015 at 10:25 AM, Ćukasz Rekucki <lrekucki at gmail.com> wrote: > Maybe instead of trying to decide who is "wrong" and which approach is > "broken", Python just needs a more clear separation between timezone > aware objects and "naive" ones? Well, the separation is pretty clear already. Tim wants to have naive timezone aware objects, ie datetime objects that have a time zone but ignores the time zone, except when converting to other time zones. I have yet to see a use case for that. //Lennart
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