Steve Dower <steve.do...@python.org> added the comment:
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? ---------- stage: patch review -> backport needed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45022> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
