Explore >> Select a destination
|
You are here 
|
adamj.eu | ||
| | | | |
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 | |
| | | | |
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. | |
| | | | |
www.cybershu.eu
|
|
| | | | | If you work with Python, you probably need to activate a virtual environment to manage dependencies. Using a virtualenv requires activation each time you wan... | |
| | | | |
wittchen.io
|
|
| | | Introduction I have my own tiny Python project called spotify-cli-linux, which is (surprise!) command line interface for Spotify desktop app on Linux. Python is not my primary programming language and I work more with Java. Nevertheless, I find this language enjoyable and useful in many cases, so I try to learn something new about it from time to time. In the beginning, I've provided instructions how to install my Python script in the system via curl and wget, which is fine, but it's not recommended and ... | ||
