this post was submitted on 06 Nov 2024
202 points (98.1% liked)
Programming
17522 readers
310 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How to improve Python packaging, or why fourteen tools are at least twelve too many
Still relevant.
https://xkcd.com/1987/
No it's not. E.g. nobody who starts a new project uses setup.py anymore
OP seems to be trying to install older projects, rather than creating a new project.
Are you sure? I'm not very active in that ecosystem, but if that was prevalent in the past, surely there's still tutorials and stuff out there that people would follow and create such projects even today?
More than that, it seems to me that the official python docs for packaging [still] talks about setup.py. Why would people not use that?
Sure, there was some hyperbole. Some people need some specific setuptools plugin or something. Almost nobody.
when the official docs are telling you to use it, then it's used. You can have no expectation of people to think the tooling isn't shit when it's literally the official recommendation.
It doesn't. read the first words behind the link you posted:
Here is the actual one: https://packaging.python.org/en/latest/tutorials/packaging-projects/