We have discussed this item in community forum and community meetups. Capturing
some of the takeaways here. Right now the set of tests we have are a bit mixed
together that causes things to slow down and mix of more recent modules with
legacy ones. In many cases, it is also tempting to just comp
We can remove the 3.7 here from tehe build env
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/15346#issuecomment-1640672545
You are receiving this because you are subscribed to this thread.
Message ID:
My guess would be that because the Conda build uses `3.7` of Python, it isn't
receiving newer builds of Cython.
https://github.com/apache/tvm/blob/e2d65111616dfa95797c0dd7e082e4050b71701d/conda/build-environment.yaml#L28
That may be quite concerning given `3.7` just passed end of life
(https://
Windows and MacOS builds are failing as they use cython==0.29.28 which is not
compatible with the new `noexcept` keyword. This functionality was added in
0.29.31
(https://github.com/cython/cython/blob/master/CHANGES.rst#02931-2022-07-27). We
could either upgrade the Windows and MacOS builds to
Thanks for contributing to TVM! Please refer to the contributing guidelines
https://tvm.apache.org/docs/contribute/ for useful information and tips. Please
request code reviews from
[Reviewers](https://github.com/apache/incubator-tvm/blob/master/CONTRIBUTORS.md#reviewers)
by @-ing them in a c
Cython `v3.0.0` was recently released
(https://github.com/cython/cython/releases/tag/3.0.0) and is used in newly
built docker images. This causes a compilation issue since 3.0.0 expects
function definitions to be explicitly declared with the `noexcept` annotation.
This change should be backward
