[Python-checkins] peps: PEP 0431 withdrawal.

[guido.van.rossum]

https://hg.python.org/peps/rev/7eb9d7413960
changeset:   5914:7eb9d7413960
user:        Guido van Rossum <guido at python.org>
date:        Wed Jul 29 19:00:15 2015 +0200
summary:
  PEP 0431 withdrawal.

files:
  pep-0431.txt |  20 ++++++++++----------
  1 files changed, 10 insertions(+), 10 deletions(-)


diff --git a/pep-0431.txt b/pep-0431.txt
--- a/pep-0431.txt
+++ b/pep-0431.txt
@@ -4,7 +4,7 @@
 Last-Modified: $Date$
 Author: Lennart Regebro <regebro at gmail.com>
 BDFL-Delegate: Barry Warsaw <barry at python.org>
-Status: Deferred
+Status: Withdrawn
 Type: Standards Track
 Content-Type: text/x-rst
 Created: 11-Dec-2012
@@ -19,17 +19,17 @@
 with ambiguous time specifications during DST changes.
 
 
-Postponement
-============
+Withdrawal
+==========
 
-The implementation has turned out to be exceedingly complex, due to having to
-convert back and forth between the local time and UTC during arithmetic
-and adjusting the DST for each arithmetic step, with ambiguous times being
-particularly hard to get right.
+After lengthy discussion it has turned out that the things I thought was 
+problem in datetime's implementation are intentional. Those include
+completely ignoring DST transistions when making date time arithmetic.
+That makes the is_dst flags part of this PEP pointless, as they would
+have no useful function. ``datetime`` by design does not separate between
+ambiguous datetimes and will never do so.
 
-This is likely to become much easier if the UTC timestamp is stored internally
-and used for all arithmetic, and an investigation into changing the
-``datetime()`` object to use UTC internally should be done.
+I therefore withdraw this PEP.
 
 
 Proposal

-- 
Repository URL: https://hg.python.org/peps