#13870: Undo #715, #11521
-------------------------------+--------------------------------------------
       Reporter:  jdemeyer     |         Owner:  robertwb                      
           Type:  enhancement  |        Status:  new                           
       Priority:  major        |     Milestone:  sage-duplicate/invalid/wontfix
      Component:  coercion     |    Resolution:                                
       Keywords:               |   Work issues:                                
Report Upstream:  N/A          |     Reviewers:                                
        Authors:               |     Merged in:                                
   Dependencies:               |      Stopgaps:                                
-------------------------------+--------------------------------------------
Description changed by jdemeyer:

Old description:

> #715, #11521 are causing a lot of trouble with various tickets.

New description:

 My feeling is increasing that Sage isn't ready yet for #715. I certainly
 believe that this isn't the fault of #715, but of other parts of Sage. But
 for me that's irrelevant, what matters to me is that we don't get
 unexpected segfaults.

 The latest segfault is at #13566, even with the new Cython from #13832.

 Therefore, I have created this ticket to undo #715 and #11521. At least,
 it is useful for checking whether a segfault is "caused" by #715 + #11521.
 I hope it won't be merged (note the milestone).

 Jeroen (release manager)

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13870#comment:3>
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.

Reply via email to