Explore >> Select a destination
|
You are here 
|
rgoswami.me | ||
| | | | |
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. | |
| | | | |
vickiboykis.com
|
|
| | | | | When I'm working with Jupyter notebooks, I often want to work with them from within a virtual environment. The general best practice is that you should always use either virtual environments or Docker containers for working with Python, for reasons outlined in this post, or you're gonna have a bad time. I know I have. The workflow is a little long, so I thought I'd document it for future me here. | |
| | | | |
xcorr.net
|
|
| | | | | By far the most popular post on this blog is areview of severalPython integrated development environments (IDEs)gearedtowardscience. Coming from a Matlab background, it's natural tosearch for something Matlab-like to replace it - an IDE with integrated editor, code execution, plotting, benchmarking, file management, etc. An increasingly attractive alternative is the IPython Notebook. The ipython Notebook... | |
| | | | |
github.com
|
|
| | | A terminal-based text editor written in Rust. Contribute to gchp/iota development by creating an account on GitHub. | ||
