Explore >> Select a destination
|
You are here 
|
www.rasulkireev.com | ||
| | | | |
www.silveiraneto.net
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
snarky.ca
|
|
| | | | | There are a couple of things I always want to be true when I install Python packages for a project: 1. I have a virtual environment 2. Pip is up-to-date For virtual environments, you would like them to be created as fast as possible and (usually) with the newest version | |
| | | | |
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.... | ||
