datetime.utctimetuple() method should respect fold disambiguation

[abalkin]

BPO	27711
Nosy	@abalkin

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/abalkin'
closed_at = <Date 2016-08-08.16:21:37.726>
created_at = <Date 2016-08-08.16:18:06.134>
labels = ['type-feature']
title = 'datetime.utctimetuple() method should respect fold disambiguation'
updated_at = <Date 2016-08-08.16:21:37.725>
user = 'https://github.com/abalkin'

bugs.python.org fields:

activity = <Date 2016-08-08.16:21:37.725>
actor = 'belopolsky'
assignee = 'belopolsky'
closed = True
closed_date = <Date 2016-08-08.16:21:37.726>
closer = 'belopolsky'
components = []
creation = <Date 2016-08-08.16:18:06.134>
creator = 'belopolsky'
dependencies = []
files = []
hgrepos = []
issue_num = 27711
keywords = []
message_count = 2.0
messages = ['272175', '272176']
nosy_count = 1.0
nosy_names = ['belopolsky']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27711'
versions = ['Python 3.6']

[abalkin]

With TZ = America/New_York:

>>> t0 = datetime(2016, 11, 6, 1, 30, fold=0)
>>> t1 = datetime(2016, 11, 6, 1, 30, fold=1)
>>> t0.utctimetuple()[:6]
(2016, 11, 6, 1, 30, 0)
>>> t1.utctimetuple()[:6]
(2016, 11, 6, 1, 30, 0)
>>> t0.timestamp()
1478410200.0
>>> t1.timestamp()
1478413800.0

The correct values for utctimetuple() should be the same as

>>> datetime.utcfromtimestamp(t0.timestamp()).timetuple()[:6]
(2016, 11, 6, 5, 30, 0)
>>> datetime.utcfromtimestamp(t1.timestamp()).timetuple()[:6]
(2016, 11, 6, 6, 30, 0)

[abalkin]

This would be a feature not anticipated by PEP-495.