/explore
|
You are here 
|
janakiev.com | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
jakevdp.github.io
|
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
newdevsguide.com
Let's take a look at Polyglot Notebooks and explore how we can use them to write C# code in an interactive and sharable notebook format. |
|
| | | |||
