Warning: 'brew doctor' python configuration scripts exist outside system or Homebrew directories

[robertleeblairjr]

Too many issues will kill our team's development velocity, drastically.
Make sure you have checked all steps below.

Prerequisite

• Make sure your problem is not listed in the common build problems.
• Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too.
• Make sure you are not asking us to help solving your specific issue.
  • GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
• Make sure your problem is not derived from packaging (e.g. Homebrew).
  • Please refer to the package documentation for the installation issues, etc.
• Make sure your problem is not derived from plugins.
  • This repository is maintaining pyenv and the default python-build plugin only. Please refrain from reporting issues of other plugins here.

Description

• Platform information (e.g. Ubuntu Linux 16.04):
• OS architecture (e.g. amd64):
• pyenv version:
• Python version:
• C Compiler information (e.g. gcc 7.3):
• Please attach verbose build log as gist
  • You can turn on verbose debug logging using by setting PYENV_DEBUG=1, e.g. env PYENV_DEBUG=1 pyenv install -v 3.6.4

Platform: macOS 10.15.7
OS architecture: Darwin 19.6.0
pyenv version: 1.2.21
Python version: 3.9.0
C Compiler information: Apple clang version 12.0.0 (clang-1200.0.32.21)

brew doctor
`Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: "config" scripts exist outside your system or Homebrew directories.
./configure scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
/Users/robert/.pyenv/shims/python3.9-config
/Users/robert/.pyenv/shims/python-config
/Users/robert/.pyenv/shims/python3-config`

I know this has been an open issue and something that should be ignored. However, rbenv doesn't have this warning because they don't use a *-config naming convention in their shim directory. Since pyenv is based upon handling versioning like rbenv, then it would seem that pyenv could move to not using this *-config scheme. Any chance that pyenv could change their naming conventions by not using *-config for their scripts like how rbenv handles theirs?

[NinoScript]

Duplicated #106

[robertleeblairjr]

Duplicated #106

Over a month away with no response from anyone and you replied with something I mentioned already that this has been reported before. Brilliant. That tells me this will not be resolved.

[NinoScript]

Over a month away with no response from anyone and you replied with something I mentioned already that this has been reported before. Brilliant. That tells me this will not be resolved.

Hey, sorry, I was just trying to be helpful and link this issue to the other one, this way any one seeing that issue will also see yours. I don't work here, I was just trying pyenv for the very first time and wanted to help a bit.

If this is so important to you, maybe you should try to fix it.

[robertleeblairjr]

Over a month away with no response from anyone and you replied with something I mentioned already that this has been reported before. Brilliant. That tells me this will not be resolved.

Hey, sorry, I was just trying to be helpful and link this issue to the other one, this way any one seeing that issue will also see yours. I don't work here, I was just trying pyenv for the very first time and wanted to help a bit.

If this is so important to you, maybe you should try to fix it.

Sorry for coming off as a bit pretentious. However, I knew about the other post. I just made another one. This being an ongoing nuisance which doesn't plague 'rbenv' because it doesn't use the *-config naming convention and adds to the brew shell environment. If 'pyenv' had actually been a fork which follows 'rbenv' coding, then it wouldn't have this conflict. I don't know enough about it to offer a solution against 'rbenv'. Adding an alias or changing the *-config naming resolves the issue with 'brew doctor'. Just chiming in with an issue that would provide a history of reports.

[freedev]

Hi is there any update about?

[robertleeblairjr]

Hi is there any update about?

None that I'm aware of which were patched. I don't use python now. I only installed this version manager when I was going through some self-taught lessons. I've not used it in quite some time. Is it still existing?

[imjuanleonard]

Hi is there any update about?

Try to translate this link https://www.task-notes.com/entry/20141223/1419324649 to English,

you will find out that one of the easy way is
alias brew="env PATH=${PATH//$(pyenv root)/shims:/} brew"

Hope this is helpful
Caveats, it breaks zsh-completions

[native-api]

Duplicate of #106