native-api

> > @yc2984 What's `which clang`? > > `/usr/bin/clang` > That's correct. So you don't have a wrong compiler in PATH, but you do have wrong include files in the...

> Same issue I have, was there any patches for 3.7.0? @DesAWSume You most likely have a different issue. "BUILD FAILED" is a generic message for _any_ build failure. Check...

Whatever this `/usr/local/include/stdbool.h` is, it's broken. Get rid of it. I checked that `stdbool.h` that come with Homebrew's GCC or LLVM do not have that line, and are not symlined...

Prepending shims to PATH is essential for Pyenv's transparent switching mechanism. It was always in the suggested configuration. #1898 just moved prepending it to a different moment. If you provide...

The thing is, the two-step configuration introduced in #1898 has proven to be too complicated and inconvenient for way too many users for comfort. So we reduced it back to...

Yes, I agree that `--no-path` looks like a trivial fix for such a case. (I don't think we need anything more complicated until an appropriate use case arises.) Could you...

> 1. Can we ask users to exec a login shell? i.e. `exec $SHELL -l` Since new terminal tabs/windows may be opening non-login shells -- no :slightly_smiling_face: . Too complicated...

> 2\. That's an interesting one. It's neither login nor interactive. Will look into it. Worse. [In some distros (notably Debian-based and Fedora), Bash is configured to run `~/.bashrc` when...

> Considered that as well as `--no-path`. I meant "considered when designing #2310". So if it works for you better, fine with implementing that, too.

> not moving shims to the beginning of the `PATH` if it's already there I should have time to implement this next week. Looks like this will both fix your...