search

inducer / loopy

A code generator for array-based code on CPUs and GPUs
http://mathema.tician.de/software/loopy
MIT License
565 stars 71 forks source link

Pinning dependencies #811

Closed miguelcoolchips closed 9 months ago

miguelcoolchips commented 9 months ago

I have noticed that most of the dependencies in https://github.com/inducer/loopy/blob/bf3091bf3c040e731ec98830dc8644dd738650a6/requirements.txt are not pinned to any specific version. I wonder what the motivation behind this is and if you have considered pinning them all for having a realiable loopy version.

inducer commented 9 months ago

It's a non-goal at this point. I think pinning is a great strategy for an application (i.e., a "leaf" in the dependency DAG), but it's very restrictive (and could to contradictions) if done at the level of a library. Loopy being a library, I think it wouldn't be too helpful.

First, to state the support objective: All current main versions of the loopy and the packages it depends are tested (using weekly CI) to work together correctly.

In addition, depdencies don't ever break compatibility without generous deprecation periods, and they have "downstream" CI towards loopy to ensure this is true.

miguelcoolchips commented 9 months ago

Sounds reasonable, thanks