On Thu, Jul 23, 2015 at 5:07 PM, Guido van Rossum <guido at python.org> wrote: > Sorry for reviving this thread, but I was cornered at EuroPython with a > question about the status of this PEP. It seems the proposal ran out of > steam and has now missed the Python 3.5 train. What happened? Is the problem > unsolvable? Or could we get this into 3.6??? It turns out it's very complex to solve this when internally storing the time as the local time. Basically you have to normalize the time (ie check if daylight savings have changed) when doing arithmetic, but normalize is doing arithmetic, and you get infinite recursion. I've tried various ways to solve this but ran out of steam/brainpower. I think we should look into storing as UTC internally instead. It's a big change (and also needs handling pickles in a backwards compatible way) but I think that's the way forward. //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