[issue35501] "make coverage" should not leak coverage compiler flags to third party C extensions

STINNER Victor added the comment: It's unclear to me if it's a real issue or not. Moreover, I'm not comfortable to change the Makefile. So I just close the issue. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python

[issue35501] "make coverage" should not leak coverage compiler flags to third party C extensions

Change by STINNER Victor : -- title: "make coverage" should use leak coverage flags to third party C extensions -> "make coverage" should not leak coverage compiler flags to third party C extensions ___ Python tracker