#20471: changing some classic division to exact division in combinat folder
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  chapoton               |       Status:  needs_info
           Type:         |    Milestone:  sage-7.2
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  combinatorics          |  Work issues:
       Keywords:         |       Commit:
  python3, combinat      |  4688e6411e5506ccbcdd70d690658c4d3f26a522
        Authors:         |     Stopgaps:
  Frédéric Chapoton      |
Report Upstream:  N/A    |
         Branch:         |
  u/chapoton/20471       |
   Dependencies:         |
-------------------------+-------------------------------------------------

Comment (by jdemeyer):

 Replying to [comment:3 chapoton]:
 > I only took care of the failing doctests, not of the warnings (that
 often come from another part of sage, in fact)

 I really do not understand what you mean. In fact, it makes me doubt that
 you understood what I meant:

 if you have removed all classic divisions from the `combinat` folder, I
 recommend to put `from __future__ import division` in the source code of
 the `sage/combinat/*.py(x)` files. Doing that will ensure that no old-
 style division can sneak in with future changes. It also makes it very
 explicit that no further work needs to be done with division in those
 modules.

--
Ticket URL: <http://trac.sagemath.org/ticket/20471#comment:5>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to