Several comments about priorities and (new) policies in the Python ecosystem

Off the top of my head:

  • Another package set combination that we need to build and maintain
  • Lots of noise (newly failing packages) because packages want either numpy 1 or 2
  • We’ll eventually end up with lots of pins to that package set, for which clean up will likely fall to the package set maintainers
  • No data on whether we can make the switch, and researching it is somewhat costly, comparable with python-updates

I proposed sticking with numpy 1 for 24.11 and evaluating the switch after branch-off.

3 Likes