/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 janakiev.com
Using Virtual Environments in Jupyter Notebook and Python - njanakiev
| | www.ethanrosenthal.com
Everything Gets a Package: My Python Data Science Setup | Ethan Rosenthal
1.3 parsecs away

Travel
| | 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
Installing Python Packages from a Jupyter Notebook | Pythonic Perambulations
1.2 parsecs away

Travel
| |
| | vickiboykis.com
Lauching a Jupyter notebook from within a virtual environment | Vicki Boykis
0.8 parsecs away

Travel
| | 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.
| | geoff.tuxpup.com
How I Start: Django, Tailwind, HTMX (part 1) :: Brain Dump - Geoff's Technical Notebook
14.2 parsecs away

Travel
| How I Start: Django, Tailwind, HTMX (part 1) I wanted to try out some "modern" front-end development for a while, and I did. FastAPI is great. So is Svelte. But even though I found creating APIs that way to be a breeze, building a whole site that way felt much slower and heavier than using traditional server rendering. So I decided to give django a fair shake for a while, and I'm glad I did.