Le 25/03/2017 à 16:27, Nick Coghlan a écrit : > > However, from the point of view of making it easier for Windows devs to > debug *nix debug errors, it probably makes more sense to use clang for > the main *nix test run, and then use gcc to do the coverage run.
What's the problem exactly? Situations where MSVC is more lenient than either gcc or clang? Usually it's the reverse :-) > That setup would give: > > - all 3 default compilers running in CI (MSVC in Appveyor, clang for the > main Travis tests, gcc for the coverage run) > - Windows devs getting the friendlier clang error messages when they're > trying to debug a cross-platform compilation problem - Travis builds are longer because gcc benefits from "-Og" which clang doesn't. Regards Antoine. _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
