Question about python3-config --cflags

[zlscherr]

I've noticed that running homebrew's python3-config --cflags contains -I/usr/local/include. This occasionally causes some of homebrew's packages to leak into my builds of non homebrew software. This is because setting CFLAGS on my other builds will only append to python's CFLAGS, and /usr/local/include will be searched first.

As an example, I currently have pari installed through homebrew. I was recently building another program that built its own older version of pari, and then attempted to build the cypari python package using homebrew's [email protected]. This caused a problem since it tried to use libraries from homebrew's pari as it was found earlier in CFLAGS.

I'm curious as to why homebrew does this and if anyone has any "best practice" for how to deal with this. The only resource I've so far managed to find is a six year old issue at Homebrew/legacy-homebrew#26272.

Thanks!

[zlscherr]

I completely missed this but it is the subject of an issue from a couple of days ago:

Homebrew/homebrew-core#68352

so hopefully there will be useful feedback in that thread.