# \[RFC\] Python Dependencies in TVM CI Containers

**URL:** <https://discuss.tvm.apache.org/t/rfc-python-dependencies-in-tvm-ci-containers/9011>\
**Category:** RFC\
**Created:** [February 1, 2021, 10:57pm UTC](https://discuss.tvm.apache.org/t/rfc-python-dependencies-in-tvm-ci-containers/9011 "2021-02-01T22:57:06Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [February 10, 2021, 7:07pm UTC](https://discuss.tvm.apache.org/t/rfc-python-dependencies-in-tvm-ci-containers/9011/10 "2021-02-10T19:07:53Z")

</div>

One potential idea is we can first start with l1, which is simpler, then see if there is need to move to l4. Personally I don’t think we really need a stronger consistency of packages in CI spectrum, sometimes we might want to diversify it a bit(e.g. use different compiler such as clang/gcc). We are also producing different tlcpack binary packages for different system, so we could derive the cpu package from `ci-cpu` and gpu package from `ci-gpu`.

Additionally, most of the dependencies that are relevant should have already captured by the constraint.txt e.g. `tensorflow==1.6` so there is not a lot of room to pinning down further.

---

_[View the full topic](https://discuss.tvm.apache.org/t/rfc-python-dependencies-in-tvm-ci-containers/9011)._