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

Local / Global install #28

Open
SylvainCorlay opened this issue Jan 14, 2016 · 4 comments
Open

Local / Global install #28

SylvainCorlay opened this issue Jan 14, 2016 · 4 comments

Comments

@SylvainCorlay
Copy link
Contributor

The local choice in the installer triggers the installations of pip packages with the --user option which actually makes the installation global to the user. Indeed, packages get installed in ./local/lib/pythonX.Y/site-packages which is used by any python install of the user.

Hence, I think that this is a misleading name for the option. Maybe we should just call it user?

@jdfreder
Copy link
Member

Yeah that makes sense

@SylvainCorlay
Copy link
Contributor Author

We should probably also defaults to not making a user install.

@jdfreder
Copy link
Member

I'm okay making it not the default, but I'm curious why? I use the user install because it means you can run jupyter-devinstall without sudo. If you run jupyter-devinstall with sudo, you have to go back and chmod/own stuff for it to work non-sudo.

@SylvainCorlay
Copy link
Contributor Author

For example, if you have two python installs in your home directory.

  • anaconda
  • anaconda_dev

where anaconda has stable versions of everything, and anaconda_dev has the development versions installed via jupyter-devinstall, then you end up using the dev versions in both anaconda and anaconda_dev, because /local/lib/pythonX.Y/site-packages is checked first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants