Éric Araujo <mer...@netwok.org> added the comment: The distutils changes will not happen, we’re under a feature freeze. Cross-compilation support would need to be added to packaging, and we need to port Python’s build process to packaging too for 3.4 or 3.5. Also, it’s very hard to decide to accept one solution from the dozen of different patch sets posted on the various issues. I think this would need a concerted effort from all people who have worked on patches, with goals clearly defined in a public mailing list, then python-dev agreement (including MvL, who turns a very critical eye to such patches), then one patch satisfying the requirements.
I don’t like to reject the hard work of contributors who want to give back, but given the situation I describe above I’m inclined to close all of these bugs for now. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11365> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
