/explore
|
You are here 
|
ariya.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. | |
| | | | |
vsupalov.com
|
|
| | | | | Notes on how to set up the right python version and and isolated development environments. | |
| | | | |
newcome.wordpress.com
|
|
| | | | | I'm a little slow on the uptake with version management of language runtimes and environments. For a long time I just followed the Linux distribution convention of global versions of dependencies and compiler versions for my system. This changed during my years doing NodeJS development where the language and tools were changing daily it seemed.... | |
| | | | |
ankane.org
|
|
| | | Jupyter notebooks are a great alternative to the Rails console for doing exploratory data analysis and building predictive models. Here's how to... | ||
