#9958: Upgrade python to 2.7
---------------------------+------------------------------------------------
   Reporter:  mhampton     |          Owner:  tbd                               
              
       Type:  enhancement  |         Status:  needs_work                        
              
   Priority:  major        |      Milestone:                                    
              
  Component:  packages     |       Keywords:                                    
              
Work_issues:               |       Upstream:  N/A                               
              
   Reviewer:               |         Author:                                    
              
     Merged:               |   Dependencies:  #11156 #11236 #11244 #11264 
#11339 #11363 #11376
---------------------------+------------------------------------------------

Comment(by fbissey):

 Any failures from #11339 gives you a killed doctest, so
 {{{
 sage -t  -long -force_lib devel/sage/sage/rings/morphism.pyx
 sage -t  -long -force_lib devel/sage/sage/rings/homset.py
 sage -t  -long -force_lib devel/sage/sage/schemes/generic/scheme.py
 }}}
 could all be, a verbose run would help figure it out. By nature #11339 is
 somewhat random, not everyone see the same failures but all these are
 familiar.

 Just checking the others with my current list.

  * sage/categories/finite_crystals.py is a new one introduced in 4.7.2
 where the error message has changed slightly when using python-2.7.
  * sage/rings/integer.pyx is definitely python-2.7 related but not patched
 yet because I am not sure what should be done there.
  * sage/rings/padics/padic_capped_relative_element.pyx same thing
  * sage/combinat/e_one_star.py I had a patch but it became to fuzzy
 haven't done a new one.
  * sage/combinat/words/nfactor_enumerable_word.py python-2.7 two
 successive results are inverted, I want someone else to look at that one
 to make sure we can just do the obvious thing.
  * sage/symbolic/callable.py new in 4.7.2 change in the error message
 because we are running python-2.7
  * sage/geometry/polyhedra.py never seen that one before, can you re-run
 it and give more info on the failure?

 As you can see a few more patches are needed and apart from #11339 which
 is a big show stopper because of the crashes at least two other tests
 point to some potential problems that should be looked at.

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