#4797: Run sage -ba instead of sage -b after upgrading
------------------------+---------------------------------------------------
Reporter: mabshoff | Owner: mabshoff
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.6.1
Component: build | Keywords: upgrade cython
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Changes (by jdemeyer):
* component: packages => build
* priority: critical => blocker
* upstream: => N/A
* keywords: => upgrade cython
Old description:
> 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,
>
> Michael
New description:
We should really run {{{sage -ba}}} on upgrade and not just {{{sage -b}}}.
This is for example needed after the numpy upgrade in sage-4.6.1.alpha0,
see #9808.
(note: earlier versions of this ticket mentioned {{{sage -ba}}} only in
the case of a ''cython'' upgrade, but it's probably better to do {{{sage
-ba}}} always after upgrading -- Jeroen Demeyer).
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4797#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
