#14636: ECL spkg : dirty workarounds?
--------------------------------------+-------------------------------------
       Reporter:  Snark               |         Owner:  jdemeyer    
           Type:  defect              |        Status:  new         
       Priority:  major               |     Milestone:  sage-pending
      Component:  packages: standard  |    Resolution:              
       Keywords:                      |   Work issues:              
Report Upstream:  N/A                 |     Reviewers:              
        Authors:                      |     Merged in:              
   Dependencies:                      |      Stopgaps:              
--------------------------------------+-------------------------------------

Comment (by Snark):

 Replying to [comment:9 jdemeyer]:
 > Replying to [comment:6 Snark]:
 > > @nbruin(1) where is the ticket about the python3 transition? As far as
 I know, a few sagenb deps (notably twisted and flask if I remember well)
 and some of sage's standard packages (for example pil) are a concern in
 that matter, but I can't find the relevant ticket.
 >
 > I don't think there is a ticket yet, because it's obvious it's not going
 to happen anytime soon.

 A ticket isn't just about something which will happen just now ; it's a
 central place where ideas get gathered about an issue. In this case, a
 ticket listing what is holding back sage for the switch to python3 would
 probably be worthy.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14636#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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to