Explore >> Select a destination
|
You are here 
|
janakiev.com | ||
| | | | |
www.rasulkireev.com
|
|
| | | | | If you are using a virtual environment, you might have ome issues with Jupyter Notebook. In this post we go through proper Jupyter Setup with venv. | |
| | | | |
jakevdp.github.io
|
|
| | | | | ||
| | | | |
www.ethanrosenthal.com
|
|
| | | | | I make Python packages for everything. Big projects obviously get a package, but so does every tiny analysis. Spinning up a quick jupyter notebook to check something out? Build a package first. Oh yeah, and every package gets its own virtual environment. Let's back up a little bit so that I can tell you why I do this. After that, I'll show you how I do this. Notably, my workflow is set up to make it simple to stay consistent. | |
| | | | |
blog.nuculabs.de
|
|
| | | Hello, In this article I will introduce you to pyenv, a tool for managing python environments. Installing pyenv is pretty straight forward, you'll need to clone the repo and add the binaries to the path. For a typical Debian based distro using the Zsh shell the instructions would be: 1 2 3 4 git clone https://github.com/pyenv/pyenv.git ~/.pyenv echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zshrc Then, in order for this to take effect, you need to reload the shell with: source ~/.zshrc, or just restart your terminal. ?? | ||
