My understanding is that `version.py` role is, for a given version, generate local changes to physical files, to be merged into the source tree.
With the proposed approach, we would be relying on `setuptools_scm` to calculate the proper PEP-440 compliant version at any given time, reducing as much as possible (ideally to no more than _one_, in my opinion) the need for hard-coded version strings. The _one_ here only relates to the "fallback version", to cover the case of user who download a snapshot of the sources from GitHub, for example, and have no source control at all. I'm curious on what would be the purpose of `version.py` in a situation which we could just query the current version with `python setup.py --version`, but I'm happy to discuss, in case I'm missing some use-case. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-naming-scheme-for-tvm-versions-and-packages/6833/3) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/b748d89aacbf8de76a45ab723a69ae6224af9f75f3bb4dee53f9b6299d3d0e8e).
