Matthias Klose <d...@debian.org> added the comment: The last time I merged libffi, we were not able to build the MacOS X and Windows libffi from the upstream sources, but used the internal copy of the copy. Now that libffi 3.0.11 is released, we could
- update to this new version, see if the MacOS X and Windows builds work (there are upstream related changes) - start defaulting to the system libffi for at least some targets (e.g. linux), for which we know that almost nobody will use the internal copy No, I don't volunteer to maintain ctypes itself. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12081> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
