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 steve.dower
Recipients lukasz.langa, miss-islington, ned.deily, pablogsal, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-09-03.18:41:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630694461.76.0.687902982493.issue45022@roundup.psfhosted.org>
In-reply-to
Content
So on one hand, this change applies cleanly and it appears nothing needs to change to adopt the newer version.

On the other hand, because the libffi DLL has a different name, it changes the layout on disk. I know we don't do that (except in exceptional circumstances) after beta, but perhaps this one is safe enough? We certainly don't "support" directly accessing the libffi DLL, but it still could break users (if, for example, they load another native module that implicitly used the older libffi and would now fail to load when it's missing).

Any thoughts?
History
Date User Action Args
2021-09-03 18:41:01steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, ned.deily, lukasz.langa, zach.ware, pablogsal, miss-islington
2021-09-03 18:41:01steve.dowersetmessageid: <1630694461.76.0.687902982493.issue45022@roundup.psfhosted.org>
2021-09-03 18:41:01steve.dowerlinkissue45022 messages
2021-09-03 18:41:01steve.dowercreate