Explore >> Select a destination
|
You are here 
|
chriswarrick.com | ||
| | | | |
pradyunsg.me
|
|
| | | | | My response to the discussion topic posed in Python Packaging Strategy Discussion Part 1 had become quite long, so I decided to move it to write a blog post instead. This post then started absorbing various draft posts I've had on this topic since this blog was started, morphing to include my broader thoughts on where we are today. Note: I've updated this to cover an aspect of the recent LWN article on the topic as well. | |
| | | | |
drivendata.co
|
|
| | | | | Explaining the basic concepts and best practices for creating Python packages in early 2023 using pyproject.toml build standards. | |
| | | | |
johnfraney.ca
|
|
| | | | | Poetry, a next-generation Python packaging tool, makes it easy to create and publish a Python package. | |
| | | | |
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 ... | ||
