Conversation

Notices

1. Embed this notice
   clacke (clacke@libranet.de)'s status on Tuesday, 10-Feb-2026 22:26:08 JST clacke

   Oh, what a fun journey.

   jsonschema < 3.10 relies on pkg_resources, which was removed in setuptools 82

   so we bump lower versions of jsonschema. in some cases we get 4.17.3, haven't checked why yet. some other dependency keeps it down. that version works fine.

   in one case (one repo) we get 4.26.0, and it breaks because referencing==0.36.0 relies on TypeVar in typing-extensions having a keyword argument 'default'. that came in typing-extensions 4.4 and the repo is on 4.1.

   referencing==0.36.1 depends on typing-extensions>=4.4 to ensure it has the keyword argument, but that's exactly why pip-compile picked 0.36.0 instead. 🙈

   There's no bug to report on anyone, everything has been fixed in recent versions, and old versions can't be fixed retroactively. But if you're trying to do a normal, conservative bump, it's a little murder mystery.

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Tuesday, 10-Feb-2026 22:26:33 JST clacke

     in reply to
     It was attrs. An old attrs held jsonschema back, as jsonschema>=4.18 depends on attrs>=22.2.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Wednesday, 11-Feb-2026 20:55:42 JST clacke

     in reply to

     • hypolite

     @hypolite This is pip-compile, a separate tool. The way I usually check why something was held back is to ask it to explicitly upgrade further and see what changes that would pull in.

     When it has conflicts that prevent it from doing what I ask, the error message is usually awful, and then I double-check its work with uv pip install.

     uv pip install, basically a drop-in replacement for pip, has gloriously informative error messages and also helpful success messages, a diff output of what packages it would install and uninstall.

   • Embed this notice
     hypolite (hypolite@friendica.mrpetovan.com)'s status on Wednesday, 11-Feb-2026 20:55:43 JST hypolite

     in reply to
     @clacke Does pip have a "why" command?