Re:Should You Use Upper Bound Version Constraints (In Python)?
by adw on Tuesday April 16, 2024 @09:27PM
(#40059424)
I think they're suggesting "change the name", which neglects the value of identifiers as _things people talk about_. It's a fine approach if module names are equivalent to ISBNs, but they're not really.
[ Parent
| on HN ]
Re:Should You Use Upper Bound Version Constraints (In Python)?
by quotemstr on Tuesday April 16, 2024 @09:32PM
(#40059454)
What's the value of modeling GTK2, GTK3, and GTK4 as the "same" library with a different major version number while modeling Qt as a separate library? They're all incompatible.
Re:Should You Use Upper Bound Version Constraints (In Python)?
by adw on Tuesday April 16, 2024 @09:55PM
(#40059601)
a) most libraries are not UI frameworks undergoing significant perpetual rewrites (and a lot of the distaste towards those frameworks comes from the perpetual rewrites)
b) even given that, they share a mindset, and being able to talk about that mindset has value (trivial example: all the GTKs are GObject C libraries, Qt is a C++ thing.
You're right if and only if there is no transferable knowledge communicable by saying "GTK", regardless of version (or you're just not talking to anyone).