![]() If you run without the sudo, you are confining the danger to the user account. Generally, you would rather run root installs only with Debian packages, not with pip3. I'd warn you to not eagerly follow advice that some people here will offer, to run "sudo pip3 xxx". I don't want this to sound like a flame, but it may seem like an attack. Intended Audience :: System Administrators Requires: nbconvert, ipykernel, ipywidgets, notebook, jupyter-console, qtconsole Location: /home/pauljohn/.local/lib/python3.5/site-packages Install all the Jupyter components in one go. Shows all of the packages available, not just ones installed by pip3. One way to make sure where that was installed into is to run $ pip3 list In my case, I installed several programs with pip3, such as jupyter. I think all shells in Ubuntu will source that file. If you might use other shells, I think the right thing is to edit the ~/.profile instead. Then every time I use a BASH shell, PATH would be fixed. Note I wrote out $HOME, not "~" in there. So I could put $HOME/local/bin on the front of that. Depending on your setup, for example, in my home folder ".bashrc" file, the last line is "export PATH=$PATH:$HOME/bin". If you later decide you want to make that permanent, so that ~/.local/bin is always in your PATH, you can do that by editing some environment configuration files. No need for the "./" that you see sometimes, that's when you launch a program from the working directory which is not in the path. There is no need to run "~/.local/bin/jupyter", for example. It is a good place to test things.Īfter that, every program executable within ~/.local/bin should run if you type its name in the command line. It does not apply to other terminals at the same time or in the future. Please remember that is a temporary setting only for that terminal session. Now, add that directory to the path within the terminal $ export PATH=~/.local/bin:$PATHĬheck your path again to see the change. If those file permissions show "x" they are executable. That confirms the executable files are there, or does for me. In a terminal, type this to see your path now: $ echo $PATHĬheck that you do have the installed python stuff in ~/.local $ ls -la ~/.local/bin Its customary in Unix to divide the file types, put the "runable" ones under ~/.local/bin. Supposing you have run pip3 install whatever, it defaults to put stuff under ~/.local, as you know. I was just doing this today, seems like clear documentation is scarce for people who want to keep some control over what's installed, and where.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |