[issue16985] Docs reference a concrete UTC tzinfo, but none exists

Changes by Andrew Svetlov : -- stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailin

[issue16985] Docs reference a concrete UTC tzinfo, but none exists

Changes by Jason R. Coombs : -- resolution: -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue16985] Docs reference a concrete UTC tzinfo, but none exists

Roundup Robot added the comment: New changeset 582ecb9a4061 by Jason R. Coombs in branch '2.7': #16985: Remove incorrect phrase indication presence of non-present concrete UTC tzinfo instance. http://hg.python.org/cpython/rev/582ecb9a4061 -- nosy: +python-dev __

[issue16985] Docs reference a concrete UTC tzinfo, but none exists

Brett Cannon added the comment: Nope, no reason. I bet it was a bad merge somewhere in the docs from Python 3 to 2.7 at some point. -- ___ Python tracker ___ ___

[issue16985] Docs reference a concrete UTC tzinfo, but none exists

Changes by Ezio Melotti : -- nosy: +belopolsky, brett.cannon, rafe ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue16985] Docs reference a concrete UTC tzinfo, but none exists

New submission from Jason R. Coombs: The Python 2.7 docs for datetime state, "The standard library has no tzinfo instances except for UTC," but if I read issue5094 correctly, Python 2.7 does not even have a UTC tzinfo instance, and never will. Is there any reason I shouldn't correct the docs t