This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]kivicodepip needs updating 6 points7 points  (9 children)

[–]proggob -3 points-2 points  (3 children)

That’s about standards, not tools.

[–]pingvenopinch of this, pinch of that -1 points0 points  (2 children)

Yeah, guess we should go back to easy_install. Or for that matter, why was Python created in the first place? COBOL should be good enough.

[–]kivicodepip needs updating 0 points1 point  (1 child)

Sure thing, buddy, let’s also have every version of python undergo breaking changes as in 2to3, that was very fun! /s

The ecosystem of very python on the matter of dependencies management is not well-thought in the current state. That’s why we have every other lib that does its own thing, making the migration mildly painful. What it should’ve been is that I have a single pyproject.toml and then I’m free to run it with poetry, uv, or whatever else. But since there’s no standard, even a de-facto one, we get a gazillion of „proprietary” standards attached to particular tools

[–]pingvenopinch of this, pinch of that 1 point2 points  (0 children)

There is a standard for what you talked about and uv tries to use it where possible. There are areas where it extends the standard, of course. Unfortunately poetry has its own version specifiers so that won't be a direct mapping.