Hello everybody. In sage 8.7.b6 built with python3, there are now 464 failing doctests, in a total of 137 files. Among these files, 55 have just one failing doctest. The worst file is now 'src/sage/matroids/matroid.pyx' with 22 doctests failed.
To make further progress, one thing that we must handle is the "round" problem. See the discussion in https://trac.sagemath.org/ticket/25827 and below. To summarize: - the behaviour of python's own "round" changed between py2 and py3. In python3, it calls the method .__round__ - our rings mostly implement a method .round - round can mean two distinct things : return the closest integer like round(pi)=3 or return an approximation like round(pi,4)=3.1416 - the rounding to an integer can be ambiguous for half integers, and there are competing norms to decide what to do (up, down, away from zero, according to parity) I would appreciate if *somebody would stand up and take the job* *of caring for round*. This may fix a big bunch of doctests. My previous naive tentatives have not been received with any enthusiasm. I would rather not go on and transmit the task to people knowing the matter. Frédéric P.S. Python3 progress is tracked at https://trac.sagemath.org/ticket/26212 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
