STINNER Victor <vstin...@redhat.com> added the comment:
> If the intent is to use this issue to track the resolution of the original > issue (clang compilation broken) and cover the new PR (which just moves the > code from os detection to compiler detection), then it can remain open. > Otherwise it can be closed, as the original issue 'has' been fixed. Ok, I close the issue. On https://github.com/python/cpython/pull/5233 bapt asked "code changes", but I don't understand what exactly and I'm not interested to continue to work on these changes. If someone is interested, please open a new issue (pointing to this one). ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue20767> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
