New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename xrange() to range() #16457
Comments
New commits:
|
Author: André Apitzsch |
Commit: |
Branch: u/aapitzsch/ticket/16457 |
comment:2
I am strongly against that this ticket is being merge now. We are far from having the Python 3 switch tomorrow (is it even a blocker for sage-6.3?). It will slow down everything.
And there are many of them in Sage source code. |
comment:3
Yeah, this does seem somewhat premature due to this. However, it's still good to have a trial version here, especially if someone decided to make a 'Sage-py3' branch for testing at some point. |
comment:8
see #21375 for a step in this direction |
comment:10
NOTE: xrange can (and should) stay inside the code of .pyx files |
This comment has been minimized.
This comment has been minimized.
comment:13
This is now essentially done. There remains only very few xrange in the code. Let us get rid of them here if possible. |
Changed commit from |
Changed branch from u/aapitzsch/ticket/16457 to none |
Commit: |
Branch: u/chapoton/16457 |
comment:15
at least one bot is green, please review |
comment:16
ping ? |
Changed author from André Apitzsch to André Apitzsch, Frédéric Chapoton |
Reviewer: Travis Scrimshaw |
Changed branch from u/chapoton/16457 to |
In python3 xrange() was renamed to range().
With this patch iterators will become lists till we switch to python 3. But this should be okay for small intervals. (That's the reason for not changing all.)
This is part of #16081.
NOTE: xrange can (and should) stay inside the code of .pyx files
CC: @jdemeyer @tscrim @a-andre @embray
Component: python3
Author: André Apitzsch, Frédéric Chapoton
Branch/Commit:
dd549fa
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/16457
The text was updated successfully, but these errors were encountered: