Message370071
The behaviour change for range sounds reasonable to me.
Just to make sure I understand the impact of the change:
- For Python < 3.10, we sometimes convert the range inputs to Python ints, and sometimes don't. For example, a start value of `np.int64(5)` would be converted, but a value of `True` would not be.
- With this change, we'd always convert a non-int to an int, so both `np.int64(1)` and `True` would be converted to a `1` of exact type int.
IMO this is fine; the new behaviour seems more consistent than the old.
>>> import numpy as np
>>> start = np.int64(2)
>>> range(start, 5).start is start
False
>>> start = True
>>> range(start, 5).start is start
True |
|
Date |
User |
Action |
Args |
2020-05-27 12:41:25 | mark.dickinson | set | recipients:
+ mark.dickinson, barry, serhiy.storchaka |
2020-05-27 12:41:25 | mark.dickinson | set | messageid: <1590583285.64.0.988784065531.issue40792@roundup.psfhosted.org> |
2020-05-27 12:41:25 | mark.dickinson | link | issue40792 messages |
2020-05-27 12:41:25 | mark.dickinson | create | |
|