#17398: Changing .next() to next(...)
-------------------------------------------------+-------------------------
Reporter: aapitzsch | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: sage-6.5
Component: misc | Resolution: fixed
Keywords: python3 | Merged in:
Authors: André Apitzsch | Reviewers: Marc
Report Upstream: N/A | Mezzarobba
Branch: | Work issues:
f505b87b4c15c07ca251f9692f4da41a8a025ab6 | Commit:
Dependencies: #17460 | Stopgaps:
-------------------------------------------------+-------------------------
Comment (by aapitzsch):
Replying to [comment:11 tmonteil]:
> It is normal that, on `develop.6.8.beta1` i got at least 262 calls to
the `.next()` method ?
>
> {{{
> $ grep -R '\.next(' | wc -l
> 262
> }}}
Not all of the `.next()` method calls can be converted to `next(...)`
function, because the related object is no iterator.
I opened #18592 to convert some of the methods.
--
Ticket URL: <http://trac.sagemath.org/ticket/17398#comment:12>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
