PEP 0431 withdrawal.

This commit is contained in:
Guido van Rossum 2015-07-29 19:00:15 +02:00
parent 0990eb2b1b
commit a6dff45ad1
1 changed files with 10 additions and 10 deletions

View File

@ -4,7 +4,7 @@ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
Author: Lennart Regebro <regebro@gmail.com> Author: Lennart Regebro <regebro@gmail.com>
BDFL-Delegate: Barry Warsaw <barry@python.org> BDFL-Delegate: Barry Warsaw <barry@python.org>
Status: Deferred Status: Withdrawn
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
Created: 11-Dec-2012 Created: 11-Dec-2012
@ -19,17 +19,17 @@ Python standard library, and also improvements to the time zone API to deal
with ambiguous time specifications during DST changes. with ambiguous time specifications during DST changes.
Postponement Withdrawal
============ ==========
The implementation has turned out to be exceedingly complex, due to having to After lengthy discussion it has turned out that the things I thought was
convert back and forth between the local time and UTC during arithmetic problem in datetime's implementation are intentional. Those include
and adjusting the DST for each arithmetic step, with ambiguous times being completely ignoring DST transistions when making date time arithmetic.
particularly hard to get right. 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 I therefore withdraw this PEP.
and used for all arithmetic, and an investigation into changing the
``datetime()`` object to use UTC internally should be done.
Proposal Proposal