this post was submitted on 09 Jul 2023
0 points (NaN% liked)

Python

6343 readers
10 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
jnovinger@programming.dev
erlingur@programming.dev
norambna@programming.dev
0
How to improve Python packaging, or why fourteen tools are at least twelve too many (chriswarrick.com)
submitted 1 year ago* (last edited 1 year ago) by oscar@programming.dev to c/python@programming.dev
2 comments fedilink hide all child comments
 

I stumbled upon this while researching package management options for python, and found it a really interesting read.

I like python as a language but this mess is something that needs to be addressed for me to consider python for future projects. I can't imagine how confusing it must be for new users.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] stilgar@infosec.pub 0 points 1 year ago (1 children)

Our organisation has gone all in on Poetry, no regrets so far. The UX and dlscoverability is just so much better than the other options.

I do look jealously at languages that have great official tools like go and cargo though.

[โ€“] Blackthorn@programming.dev 1 points 1 year ago

I love cargo, but cargo.io could REALLY make good use of namespaces. It's insane when clear library names are taken by highschoolers at their first project and there is nothing to be done about it. I'd also like some kind of curating on the packages.