Explore >> Select a destination
|
You are here 
|
blog.fahhem.com | ||
| | | | |
www.pither.com
|
|
| | | | | The simple way to build a Python script and dependencies into a portable binary. | |
| | | | |
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 ... | |
| | | | |
avilpage.com
|
|
| | | | | How to build and distribute a Python C extension module using wheels | |
| | | | |
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. | ||
