➜

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 ned.deily
Recipients loewis, ned.deily, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2016-12-21.20:52:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482353563.27.0.344998042183.issue23903@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't know enough about how python3.dll is used in the Windows world to ask the right questions.  One obvious one: would this change likely affect any third-party binaries already built for 3.6.0?  On the other hand, if we have to have one, it would be better to have a compatibility break at 3.6.0 rather than at 3.6.1.  I really don't want to take any more changes at this point for 3.6.0 but if you are convinced it is the right thing to do and won't break anything, get it in for 3.6.1 now and I'll reluctantly cherrypick it for 3.6.0.
History
Date User Action Args
2016-12-21 20:52:43ned.deilysetrecipients: + ned.deily, loewis, tim.golden, zach.ware, serhiy.storchaka, steve.dower
2016-12-21 20:52:43ned.deilysetmessageid: <1482353563.27.0.344998042183.issue23903@psf.upfronthosting.co.za>
2016-12-21 20:52:43ned.deilylinkissue23903 messages
2016-12-21 20:52:43ned.deilycreate