1

I have a new Macbook - a user installed it, and then I installed a new user (mine), granted admin privileges and deleted the old one. I am on OS Catalina.

Since the installation I've been having several permission problems. VSCode can't find Jupyter Notebook, pip installs packages at ~/Library/Python/3.7/site-packages.

When I do which python3 I get usr/bin/python3. When I do pip3 install <package> I get: Defaulting to user installation because normal site-packages is not writeable And then it says it has already been installed, even though I can't access it when I do import .

It's seems clear that this is a permission problem, pip can't install to the "base" python, and them python can't find what I've installed into ~/Library/Python/3.7/site-packages.

I've tried reinstalling the OS, but since I haven't done a clean install, it didn't change anything. What am I missing? How exactly can I fix permissions? Where do I want packages to be installed (venv sure, but some packages I want global (like jupyter).

Thanks

3
  • I'd be tempted to start over - the original install will belong to the AppleID of that first user. Eventually you'll hit some point their ID is needed & you won't know it. – Tetsujin Jan 31 '20 at 15:14
  • I was afraid that would be the answer... But it does seem like the best approach... – lowercase00 Jan 31 '20 at 15:19
  • Hope that they didn't block reinstall. New Macs with T2 chips are absolutely un-bypassable unless released by the original user or failing that, Apple. [Unless it's an MDM machine] – Tetsujin Jan 31 '20 at 15:32
1

There's no reason to start over from what I can see here. This is a basic python and unix permission issue, forget that it's a mac. Given that you have admin permissions, and considering where Python is installed as well as where the packages are, I don't see a reason to do a clean install. If there were for some crazy reason (I don't think there is,) a python folder with the ownership belonging to the old user, you should be able to take ownership considering the folder isn't in their home directory, and considering the fact that you have admin/sudo abilities.

I'd start by running an "ls -lah" against ~/Library/Python/3.7/site-packages and see if there are different permissions set for your new package folder. If there are, edit them so that they're more permissive, or so that they belong to the right group.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.