Re:Modern Python Performance Considerations
by nerdponx on Thursday May 05, 2022 @07:00PM
(#31279322)
This is an overly-dire assessment in my opinion. Setuptools + Pip has been more or less stable for years, and no changes in dev environment have been needed since stability was reached. There is a lot of new stuff coming out, for people who want new stuff, but there's nothing wrong with the old stuff if the old stuff works for you, which will remain supported for several more years if not forever.
Re:Modern Python Performance Considerations
by whimsicalism on Thursday May 05, 2022 @02:44PM
(#31277043)
I think poetry actually does solve it
Oh, there are a half dozen different tools that solve python package management. Unfortunately, they are mutually incompatible and none solve it for all use cases.
Re:Modern Python Performance Considerations
by wardedVibe on Thursday May 05, 2022 @07:16PM
(#31279402)
Re:Modern Python Performance Considerations
by AlphaSite on Thursday May 05, 2022 @11:39PM
(#31281050)
It’s somewhat the opposite situation, poetry is a tool that lots of people are adopting rather than one being pushed by a standards committee. I don’t think it set out to unify a dozen standards, only build a good UX and to be reproducible.
Re:Modern Python Performance Considerations
by whimsicalism on Friday May 06, 2022 @12:50PM
(#31287308)
Poetry isn't an additional standard, more like an implementation. It is PEP 518 compliant.
If you use it as a scripting language, that might very well be the case (it's at least simpler). When you're building libraries or applications, no, definitely not. It's a huge mess, and every 3 years or so we get another new tool that promises to solve it, but just ends up creating a bigger mess.