Explore >> Select a destination
|
You are here 
|
www.blog.pythonlibrary.org | ||
| | | | |
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. | |
| | | | |
stribny.name
|
|
| | | | | [AI summary] This article explains interactive computing with Jupyter Notebooks, covering its definition, use cases for data science and education, installation methods, and how to manage kernels. | |
| | | | |
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. | |
| | | | |
wweb.dev
|
|
| | | In this post, I will show how to set up debugging for Javascript in VS Code for Node.js and for React in Firefox or Chrome... | ||
