# \[RFC\] Consolidating TVM Python Dependencies

**URL:** <https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329>\
**Category:** RFC\
**Created:** [October 29, 2020, 4:17pm UTC](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329 "2020-10-29T16:17:24Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![tqchen](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/tqchen/32/5_2.png) [@tqchen](https://discuss.tvm.apache.org/u/tqchen)\
**Post date:** [November 2, 2020, 10:52pm UTC](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/16 "2020-11-02T22:52:02Z")

</div>

The main question is whether not the exact pinpointing is critical to reproduce CI. Our previous experience seems to suggest that pin pointing the few constraints are sufficient, if not, we should add things to the constraint.txt

Notably, there are also additional environments that are not covered by the pip lock, e.g. LLVM CUDA dependencies. When we are getting to the level of exact reproduce, perhaps the easiest way is still to fall back to use the exact docker binary tag itself.

---

_[View the full topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329)._