Re: PyObjC and macOS 10.12 (Sierra)
Andrew Jaffe <[email protected]> Mon, 12 Sep 2016 09:58:31 +0100
| Newsgroups | gmane.comp.python.pyobjc.devel,gmane.comp.python.apple |
|---|---|
| Message-ID | <[email protected]> |
[Apologies if more than one copy of this message is posted!] On 11/09/2016 20:57, Glyph Lefkowitz wrote: > >> On Sep 11, 2016, at 3:12 AM, Andrew Jaffe <[email protected] >> <mailto:[email protected]>> wrote: >> >> If I do the usual "pip --upgrade" for these, it fails, seemingly >> because of permissions (Apologies, but I don't have access to the >> messages anymore): it is clearly trying to delete these versions which >> seem to live in >> /System/Library/Frameworks/Python.framework/Versions/2.7/. This fails, >> of course, due to permissions (and system integrity protection). > > This is expected, and desired, even. Don't install packages into your > system Python. Make a virtualenv and install pyobjc there, or do a `pip > install --user`. That should work fine. Sorry if I'm not being clear. I'm using python.org framework python, which supplies its own pip, and its own location for packages: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages In the past, upgrades have never been a problem, so I don't know if anything has changed with the latest macOS, or the latest pyobjc, or the latest python build, or... And I don't know if the "--ignore-installed" solution is a workaround, or actually the right answer. (I do know about virtualenv, but I don't think that's the route I want to go at this point, and I'm pretty sure I shouldn't have to.) Yours, Andrew ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot