@mjs thanks for your reply! I agree we should avoid overly restrictive version constraints in our released packages. my thoughts are that specifying a range for semver packages and especially complex dependencies with significant API exposure to tvm (I.e. most frontend packages--tensorflow, torch, etc) would be a good idea in the spirit of producing a working install. i'm happy to back off of that approach given evidence to the contrary.
i've had a similar experience with pipenv as you have in the past. i've liked poetry better so far. my thoughts are that auto-generating e.g. `requirements.txt`, `requirements-frontend-torch.txt`, etc. from a `pyproject.toml` or equivalent config would alleviate any problems with developers disliking a not-yet-standard tool such as `poetry`. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-consolidating-tvm-python-dependencies/8329/8) 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/56833e84b5219f4aad3acb6263556af348a37f817e92709ff3cba498952ac4a0).
