it's not really a question that has a general answer. sometimes pinpointing doesn't matter and other times it does. as an extreme case, pylint cannot be reproduced without both precise pinpointing of both python packages and the interpreter itself. that's why it can be hard to lint locally now (docker/lint.sh doesn't work with git-subtree). most times, the interpreter version doesn't matter so much.
we should also consider the case of using TVM with in conjunction with a project repo (I.e. not just using TVM in its source tree). in this case, suppose additional python packages need to be installed, some of which are large. you may prefer not to pay the cost of starting with ci-gpu, itself a 17.4GB image. instead, you may want to pick and choose the dependencies, and point `pip` at a constraints file that lists the exact versions of packages that were installed. anyway, I think this discussion is more about the CI flow which should go in another RFC. I think we both do agree that `ci_constraint.txt` is a reasonable thing to do to add constraints used to build CI docker images above those specified in `requirements.txt`. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/17) 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/e7dc1d3055999c88bae227f34a5501b47b7714feca006b556ab7625e93c25bd8).
