Author p-ganssle
Recipients belopolsky, p-ganssle, vstinner
Date 2018-12-07.19:49:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544212147.54.0.788709270274.issue32417@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, that's my mistake. I have always been under the impression that "Versions" meant "versions affected", not "versions that this needs to be fixed for". I usually just selected the ones where I had verified that it's a problem.

I do not think this should be backported to 3.6. From the discussion in the datetime-SIG mailing list, we have realized that this change will *also* break anyone whose default constructor does not support the same signature as the base datetime. I think this is probably not a major problem (many other alternate constructors assume that the constructor accepts arguments as datetime does), but it's not something that I think we should be changing in a patch version.
History
Date User Action Args
2018-12-07 19:49:07p-gansslesetrecipients: + p-ganssle, belopolsky, vstinner
2018-12-07 19:49:07p-gansslesetmessageid: <1544212147.54.0.788709270274.issue32417@psf.upfronthosting.co.za>
2018-12-07 19:49:07p-gansslelinkissue32417 messages
2018-12-07 19:49:07p-gansslecreate