Thanks @areusch I still think having a manually specified `ci_constraint.txt` is easier than having a resolver to pin the version. This is the way we pin dependencies right now, the developers have clear expectations about what to happen(regardless of the dep resolver's behavior) and we do not need to involve a lock file that might complicates the docker build.
--- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/12) 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/5eb2258ecf3dfdc6d334f32e53d2f9c91866a04a6f38a63443c7d79a819e46ad).
