Explore >> Select a destination
|
You are here 
|
techtldr.com | ||
| | | | |
ljvmiranda.micro.blog
|
|
| | | | | I'm now a uv convert. I haven't really updated my Python tooling and workflow for the past two years. In fact, I've been using the same workflow ever since I started working: python -m venv venv source /venv/bin/activate # While in venv pip install -r requirements.txt But there's a lot of limitations in this workflow. For example, I'm limited by the Python version installed in my machine or it's hard to just install ad-hoc dependencies for my one-off scripts. | |
| | | | |
janakiev.com
|
|
| | | | | Python's built-in venv module makes it easy to create virtual environments for your Python projects. Virtual environments are isolated spaces where your Python packages and their dependencies live. This means that each project can have its own dependencies, regardless of what other projects are doing. | |
| | | | |
128bit.io
|
|
| | | | | Over the past couple months, I've been working on fine tuning my Python skills, part of this has been taking tutorials online along with building some applications. One of the things I've been wanting to document, mostly for myself, is setting up a new environment for developing with Python. I'm using macOS Sierra right now, it seems that most operating systems still comes with version 2.x of Python. It's always a good idea to be able to control the version of Python you are using. | |
| | | | |
earthly.dev
|
|
| | | This tutorial explains how to create a Python virtual environment using PyInstaller, a packaging tool for Python applications, and distribute them ... | ||
