On Thu, Jan 26, 2017 at 8:13 PM, Nils Bruin <nbr...@sfu.ca> wrote: > On Thursday, January 26, 2017 at 12:02:07 PM UTC-8, Frédéric Chapoton > wrote: >> >> >> Please, tell me how to change the zip behaviour in the code. Or just >> change the branch if you know how. >> >> If I understand correctly, part of your question is "how do I get zip to > behave line Py3 in the doctests". > > It's a bit of a puzzle, but somewhere in sage.doctest.control there is > code that assembles the doctests into a file to be fed to python. In > principle, it should be possible to insert a "from future_builtins import > zip" into those files. >
But that won't help when the code is actually being run, not in doctests. I agree that the doctesting behavior can be changed (as a guess, something around line 2122 of sage/doctest/forker.py). David -- > 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. > -- 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.
