-
Notifications
You must be signed in to change notification settings - Fork 311
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
Issue installing on macOS Sierra #274
Comments
I'm going to guess the offending dependency is tqdm. I believe a workaround would be to install in a virtualenv instead of system-wide. I just installed a tqdm update this morning in a virtualenv as a regular user on OS X 10.13 with no issues, and sure enough, there's a $VIRTUAL_ENV/man/man1/tqdm.1 file. |
Hrmmm, looks like all that was needed was for the directory to exist. So I did Thanks for the suggestion, @jamadden, but it would be useful for |
I'll just leave a note here for macOS users running with SIP (system integrity protection) enabled (the default), and rightly using homebrew or other non-system Python (smart!), create the /usr/local/man` directory manually before pin-installing twine. |
I use a Homebrew-installed version of Python (2.7.13) on macOS Sierra (10.12.6) symlinked to
/usr/local/bin/python
. This avoids having to turn off the system integrity protection for recent macOS versions, since everything gets installed in/usr/local/bin
. Generally, I canpip install
packages I want available to use in Python whenever I'm not in a particular virtualenv, such asrequests
, etc.However, I was unable to install
twine
because some dependency wants to write to/usr/local/man
. Is there a known workaround without disabling SIP or usingsudo
?See bash output and pip stack trace below:
The text was updated successfully, but these errors were encountered: