June 2025 Python Dependency update#1024
Conversation
In addition to general updates, there was a number of additional analyzer updates and more precise pinning.
|
I'd be happy to turn off dependabot as well -- those PRs just seem like noise. |
ericholscher
left a comment
ericholscher
left a comment
There was a problem hiding this comment.
This seems fine, but it seems it's adding dependencies while also updating them? Also, we should really note why we're doing an upper pin on things, otherwise we'll have no idea why/when we can update them.
| beautifulsoup4 | ||
| textacy | ||
| spacy | ||
| spacy[transformers] >=3.8.7,< 4.0 |
There was a problem hiding this comment.
We should add a comment whenever we pin something noting why it's pinned.
requirements/analyzer.in
Outdated
|
|
||
| # Used to parse web pages and get the "main section" of the page | ||
| trafilatura | ||
| trafilatura >= 2.0.0,<3.0 |
There was a problem hiding this comment.
Similar here -- guessing this is an API breakage?
|
|
||
| # Numpy v2 has some breaking changes (for now) | ||
| numpy<2 | ||
| sentence-transformers >= 4.1,<5.0 |
There was a problem hiding this comment.
Also here? Lots of pinning here we're doing?
I'll add notes. There isn't a lot of reason for an upper pin other than to avoid breaking changes. If a major version has breaking changes, shouldn't we be careful in taking them? The minimum pin on some of these is required because versions conflict with other modules. |
2 participants
In addition to general updates, there was a number of additional analyzer updates and more precise pinning.