here's what I don't like about I1: - it doesn't ensure dependency versions are compatible across all the various extras in each container architecture - it still means that `ci-lint` or `ci-gpu` could wind up with different package versions from `ci-cpu`
I do agree that most of the large direct dependencies are quite pinned, and we could probably accomplish a lot from a ci-constraints.txt which just explicitly pins those direct dependencies. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-python-dependencies-in-tvm-ci-containers/9011/11) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/40d0a9c2d691a03b4c2be45885f95f838c7ada36cdcaa30fdaa9eb0bcbfb61d5).
