This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
[brew doctor] remove check_for_pydistutils_cfg_in_home #31827
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This check is essentially noise since the associated issue is closed. Further, I don't think the
check_for_pydistutils_cfg_in_home
was correctly depicting the bug as reported anyhow. The real issue as noted by the OP of the issue was that he had puthome
in that file which was causing the issue.The
check_for_pydistutils_cfg_in_home
method is not adequate. It actually just checks that the file~/.pydistutils.cfg
exists. This was not the issue.Further, I have a
~/.pydistutils.cfg
file and the contents are the following:I was only able to install
powerline
after having this set. I'm sure there are a ton of different variations out there. This being the case, perhapsbrew
cannot or should not attempt to get into such things since there are too many variables in play.