Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Homebrew and Python" mentions a bug in distutils without linking to a bug report #4165

Closed
nchammas opened this issue May 13, 2018 · 4 comments
Labels
outdated PR was locked due to age

Comments

@nchammas
Copy link

Over here the docs say:

The normal pip install --user is disabled for brewed Python. This is because of a bug in distutils, because Homebrew writes a distutils.cfg which sets the package prefix.

It would be helpful if the text "a bug in distutils" linked to a bug report against distutils describing the problem in detail. That would help users understand the nature of the problem and advocate for an upstream fix.

I raise this issue here because some Python projects don't work well with Homebrewed Python, typically hitting up against the following error:

distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both

Trying to get to the bottom of the issue leads to the "Homebrew and Python" documentation page, but the trail goes cold at the above mention of that bug in distutils.

@MikeMcQuaid
Copy link
Member

I don't know what this bug is so can't link to it. Maybe @tdsmith does.

In future please fill out the issue template, thanks.

@tdsmith
Copy link
Contributor

tdsmith commented May 13, 2018

you may enjoy pypa/pip#2683 and pypa/pip#4390

@nchammas
Copy link
Author

In future please fill out the issue template, thanks.

@MikeMcQuaid - My apologies. I didn't think my issue fit either of the two templates, but in the future I'll just file similar issues as bug reports.

@tdsmith - Thanks for the links. Reading through them, it looks like the referenced "bug in distutils" is perhaps this one.

@MikeMcQuaid
Copy link
Member

@nchammas Thanks! If @tdsmith can confirm it's the correct bug: could one of you submit a PR to add it to the docs? Cheers!

@lock lock bot added the outdated PR was locked due to age label Jun 13, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jun 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

No branches or pull requests

3 participants