Run sage -ba instead of sage -b after upgrading Cython

[sagetrac-mabshoff]

We should really run sage -ba when we upgrade Cython and not just sage -b.

CC: @robertwb

Component: build

Keywords: upgrade cython

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/4797

[sagetrac-mabshoff]

Description changed:

--- 
+++ 
@@ -1,4 +1,4 @@
-When upgrading Cython like at #4639 we should really run a -ba on upgrade and not just a -b since the new Cython version in this case does fix some fundamental issues the way exceptions are handled. In general I would be sleep much better if we do this in general since many potentially odd Heisenbugs that disappear after either a partial -b or a -ba would be avoided that way.
+When upgrading Cython like at #4639 we should really run a -ba on upgrade and not just a -b since the new Cython version in this case does fix some fundamental issues the way exceptions are handled. In general I would sleep much better if we do this in general since many potentially odd Heisenbugs that disappear after either a partial -b or a -ba would be avoided that way if a new Cython version is involved.
 
 Cheers,
 

[sagetrac-mabshoff]

comment:3

I can live with this issue being fixed in 3.3 since we will not upgrade Cython in 3.2.2->3.2.3.

Cheers,

Michael

[sagetrac-mabshoff]

comment:4

Ooops. Reassigned this time :)

Cheers,

Michael

[williamstein]

comment:5

Does anybody have any idea how to implement this? Here is one idea. We make it so there is a command like "sage -ba" that doesn't actually rebuild the sage library, then we make the cython spkg-install call that command. It could be called "sage -ba_nobuild" or something. This is way better, I think, than "sage -ba" trying to detect if cython was upgraded.

The disadvantage is that it might make testing installing the cython SPKG inconvenient.