On Sat, Aug 8, 2020 at 8:15 PM Jonathan DEKHTIAR <cont...@jonathandekhtiar.eu> wrote: > > So do you plan on "managing" which version of GCC or g++ people have and > issue a warning if they don't have the good one?
A setup.py will always be written for a particular compiler, or maybe it will handle a couple, but they never handle a "general compiler". That was why the example in spec Requires-External C never made sense. It always should have been something like Requires-External gcc (>4.0) There is no logic available at that level, as far as I can tell. So if a package needed gcc on Posix or an MS compiler on windows how would one specify that? For that matter, if it could use either gcc or Intel's compiler on Posix how would that be indicated? Maybe there is some specification level logic which can be used to wrap these statements? >How are you even supposed to find out? pkg-config, in any Posix environment. Within a pure Windows environment or on some obscure OS, I have no idea. Just skip this test if it is not supported in a given environment? Better that it works in some environments than in none. > > Don't get me wrong would be awesome if it worked. I just don't see a way to > handle all these contraints ... I would be happy if it handled _any_ of these constraints. At the moment adding these lines does nothing. Regards, David Mathog -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/MPHOUVI5WOEX7J5HWFBK5JQBQS46T3NX/
