/explore
|
You are here 
|
hynek.me | ||
| | | | |
v5.chriskrycho.com
Semantic Versioning, library & framework evolution, programming language design, type systems, and you. |
|
| | | | | ||
| | | | |
tom.preston-werner.com
|
|
| | | | | ||
| | | | |
iscinumpy.dev
Bound version constraints (upper caps) are starting to show up in the Python ecosystem. This is causing real world problems with libraries following this recommendation, and is likely to continue to get worse; this practice does not scale to large numbers of libraries or large numbers of users. In this discussion I would like to explain why always providing an upper limit causes far more harm than good even for true SemVer libraries, why libraries that pin upper limits require more frequent updates rather than less, and why it is not scalable. After reading this, hopefully you will always consider every cap you add, you will know the (few) places where pinning an upper limit is reasonable, and will possibly even avoid using libraries that pin upper limits ne... |
|
| | | | | ||
| | | | |
datasette.io
A command-line utility for taking automated screenshots of websites |
|
| | | |||
