|
You are here |
www.laac.dev | ||
| | | | |
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] A guide explaining how to install and manage Python development versions on Fedora using the Pyenv tool. | |
| | | | |
humberto.io
|
|
| | | | | Discover the external dependencies to use at your Python development environment on Ubuntu | |
| | | | |
www.integralist.co.uk
|
|
| | | Introduction Virtual Environments Creating Virtual Environments Installing Python Versions Virtual Environments for multiple Pythons Shell Configuration Managing Dependencies Caching Dependencies Command Line Packages Introduction This blog post aims to demonstrate the most practical way to install multiple versions of Python, and of setting up 'virtual environments' for macOS userso We'll also dig into how to manage our project dependencies (e.g. we'll be discussing the classic Pip and requirements.txt ... | ||