Gonzalo Tornaría

I think you missed one hunk in the last merge: ```diff --- a/src/sage/rings/integer.pyx +++ b/src/sage/rings/integer.pyx @@ -5585,7 +5585,7 @@ cdef class Integer(sage.structure.element.EuclideanDomainElement): sage: 5.is_norm(K) False sage: n.is_norm(K, element=True) - (True,...

@antonio-rojas Two more doctest fixes: 0a0be0cf9e3 and 6d00b9c81a0 With this + all, I have everything working just fine :tada: https://github.com/void-linux/void-packages/pull/51902 In case it's useful to someone else, I have a...

> Shouldn't this also bump cysignals to the latest released? Note that cysignals 1.12.2 doesn't work well with cypari2, as mentioned here: https://github.com/sagemath/cysignals/pull/181#discussion_r1904885037 There I proposed a solution, which works...

> Thanks. How does one force re-running the CI? push a new head (e.g. use amend to redo the last commit so its hash changes)

It won't emit a warning if written like: ```cython cdef void f() noexcept: try: raise RuntimeError() except: pass ``` The way you wrote it makes it obvious that the code...

> I wasn't really able to work out what the issue was in that linked Sage issue. > > It's safe to raise an exception inside a noexcept function -...

Maybe it's worth adding a test example as in https://github.com/cython/cython/issues/6335#issue-2459632294 ``` $ cat a.pxd cdef int f() $ cat a.pyx cdef int f(): pass $ cython -3X legacy_implicit_noexcept=True a.pyx warning:...

> > I really don't know how to reliably run tests locally, so I can't really test such a test > > In the Cython directory just checked out from...

I added a test that shows #6535 is fixed.

> I've reverted this for now because it was causing quite a few false positives when building Cython itself, so wasn't as specific as we hoped. How so, can you...