#21110: Py3 : Handle the changes to "next()" again
-------------------------+-------------------------------------------------
Reporter: | Owner:
chapoton |
Type: | Status: positive_review
enhancement |
Priority: major | Milestone: sage-7.3
Component: | Resolution:
python3 |
Keywords: | Merged in:
Authors: | Reviewers: Travis Scrimshaw
Frédéric Chapoton |
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/21110 | bed8d73c8630aa1f9a12d75e66e509c8495be83c
Dependencies: | Stopgaps:
-------------------------+-------------------------------------------------
Comment (by chapoton):
Replying to [comment:3 jhpalmieri]:
> If I search the source for `'\.next('`, I find lots of matches. Do some
of these need to be changed, also? (Some may depend on #18802, I guess.)
Only the instances of ".next()" with no arguments need to be considered. I
have carefully looked at all of them to see when they involved an
iterator. There is just once case where it seems that one could use the
`next(bla)` syntax, but which does not work. I have marked it with "bug"
in my branch. This may be the subject of a follow-up ticket.
--
Ticket URL: <https://trac.sagemath.org/ticket/21110#comment:4>
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.
