[issue13957] parsedate_tz doesn't distinguish -0000 from +0000

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

This is fixed already in 3.3.  It is a behavior change that could theoretically cause some problems.  Currently, you can think of None as meaning "there was no timezone info at all", which is subtly different from -0000, which means "this time is UTC, but I don't know what timezone it originated from".  These two tend to be conflated in practice (how else are you going to interpret a time with no timezone attached?), and since we are making other additions to email in 3.3 we decided it was a small enough change that it was OK for a dot release.  But not for a maintenance release, just in case.  (I'm open to argument on that, but these backward compatibility calls are notoriously hard to make.)

----------
assignee:  -> r.david.murray
nosy: +r.david.murray
resolution:  -> out of date
stage:  -> committed/rejected
status: open -> closed
versions: +Python 3.3 -Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13957>
_______________________________________