# \[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:** 2

<div class="post-metadata">

**Author:** ![tkonolige](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/tkonolige/32/1972_2.png) [@tkonolige](https://discuss.tvm.apache.org/u/tkonolige)\
**Post date:** [October 29, 2020, 6:48pm UTC](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/2 "2020-10-29T18:48:03Z")

</div>

I am a fan of approach A2. It seems like the python community is moving towards using poetry, and the poetry format is a lot nicer than requirements.txt for specifying dependencies. If we autogenerate requirements.txt, then everyone can use their preferred development tools.

Can poetry build the C++ part of TVM? If so, that might be a good way to make it easier for new people to start hacking on TVM.

---

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