3 ms·
No. I’m speaking in the general sense not to get hung up on an arbitrary number as the sole indicator of whether software is suitable for use in a production en
by Apreche 1y ago
No. I’m speaking in the general sense not to get hung up on an arbitrary number as the sole indicator of whether software is suitable for use in a production environment.
- ashishb 1y agoExactly.
- its-summertime 1y agoUv provides no support period of bugfixing for the previous minor release after a breaking change. So if a breaking change does occur, you must immediately update your entire world, test, etc, to continue to receive fixes. (unfortunately the norm for python projects). This is from their own documentation and release history. I never brought up version numbers before now, only their self-admitted unstable status. Version numbers were brought up by someone of the opinion that uv is stable enough.
- ashishb 1y ago> (unfortunately the norm for python projects). Yeah, that's how it is because it is costly for maintainers to maintain. What's your point though, is poetry better in this regard or what are you suggesting as a better alternative to uv?
- its-summertime 1y agoif I was asked to deploy python code? My alternative would probably be crying. Personal deployments? I'd probably go with pip hash installs ideally only of wheels, assuming that this would leave the environment in a reproducible state, probably wouldn't though. pip has the same problem as uv in this regard, but I'd be hoping that there would be less breaking from breaking changes, due to the amount of people depending on pip not breaking. If I had money? I'd fork pip or uv and assign some people to make an downstream with extended support.