Thank you for the quick response and explaining why this happened. The whole situation makes sense to me in the context of a project maintainer and DevOps perspective.
But for a normal user, this is a case of "oh it didn't work, their packages are broken" which does not give a good first impression. Worst of all, the PyPi index shows that there is a 0.12.0 release which confuses people (on x86_64, Linux) without seeing the file list. Until the binary situation is solved, a source distribution (sdist) can be released (yes the tarball is there but sdist is PIP friendly ;)), then if a platform does not have the binary wheels, it would trigger a compile, while not optimal would still make it clean to use. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/issues/15331#issuecomment-1646567662 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm/issues/15331/1646567...@github.com>
