I agree, at a high level having a constraint.txt would be sufficient in most
cases. In the case of pylint, while it is true there might be some python
version dependent errors, most cases they are not inconsistent with each
other(with the correct pylint version) and the error message produced
thanks for all the discussions! here are the next steps I can see:
1. create a `python/requirements.txt` for the core direct dependencies, specify
version constraints as appropriate to be used in the CI. also create e.g.
`python/requirements-tflite.txt` files (one per extra feature of TVM) in
Looks good to me. Given the collections of requirements does it makes sense to
create a requirements folder?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/20)
to respond.
You are receiving this because you enabled mailing list mode.
To
sure, `python/requirements/requirements.txt`?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/21)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tv
how about `python/requirements.txt` to follow normal convention, and then
`python/extra-requirements/tflite.txt`
Alternatively, we can move all the extra requirements into a single file, given
that it is relatively tedious for users to install separately anyway. They can
cherry pick if they w
