-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
get rid of part of itervalues #29103
Comments
Branch: u/chapoton/29103 |
Commit: |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
green bot, please review |
comment:5
I am not sure we should be doing this yet given that 9.1 will still be supporting Python2. Although I believe from the sage-devel discussion, are considering 9.0 the last properly Python2 supported version of Sage. So by that, it would be good to do it now. Although if 9.1 is the last such one, then we should wait a little bit I think. |
comment:6
I did that carefully in such a way that this remains fully python2-compatible. |
comment:7
Sorry, my response was poorly phrased. I meant the efficiency aspects with entire lists being created and returned in Python2 with these changes. I agree that it is fully Python2-compatible, but there will be a speed/memory difference between the two. Admittedly, this is not a very strong position considering the cases where this would matter are somewhat rare IMO. If you think that we should go ahead with only caring about Python3 at this point in time, then we can set this to a positive review. |
Reviewer: Travis Scrimshaw |
comment:8
I think that people cannot both ask for speed with python2 and use the latest sage.. Therefore setting to positive |
Changed branch from u/chapoton/29103 to |
after #29077
There are much more cases, so only half of them is taken care of.
CC: @tscrim @jm58660
Component: refactoring
Author: Frédéric Chapoton
Branch/Commit:
cbb20e6
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/29103
The text was updated successfully, but these errors were encountered: