This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author p-ganssle
Recipients alexandre.vassalotti, belopolsky, bronger, eddygeek, gregory.p.smith, p-ganssle, pitrou, serhiy.storchaka,, tim.peters
Date 2018-12-07.16:35:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@Serhiy Any chance we can roll these back before the release so that they can have some time for discussion? I have serious concerns about having to support some Python 2/3 compatibility hack in datetime for the next 6 years. If this is worth doing at all, I think it can safely wait until the next release.
Date User Action Args
2018-12-07 16:35:28p-gansslesetrecipients: + p-ganssle, tim.peters, gregory.p.smith, belopolsky, pitrou, bronger, alexandre.vassalotti, serhiy.storchaka, eddygeek,
2018-12-07 16:35:28p-gansslesetmessageid: <>
2018-12-07 16:35:28p-gansslelinkissue22005 messages
2018-12-07 16:35:28p-gansslecreate