Great to see this tricky topic is being tackled!
As the text above states, "the defacto standard Python package manager is pip". Despite it's limitations, at this current point in time, that fact is unavoidable. Users expect "pip install foo" to reliably install a working instance of foo. They also expect to be able to co-install foo with other packages, which makes packages with overly restrictive version constraints un-popular, version constraints should be sufficient to deliver a viable tool install, but no more. If seems reasonable that as a project, if necessary, we might impose the use of a specific package manager on *developers* but attempting to impose a "not yet mainstream" package manager on users will limit the reach of the project. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/6) 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/b2aedebdcd7cee76d37e92e1af19f02c3e9d8c4f5dd9cb523429850ab5baa2e6).
