py3: Adapt Sage's range-like functions

[slel]

Python 2 had range (returning lists) and xrange (returning iterators).

Python 3 only has range which behaves like the old xrange.

This ticket is to rename or change our range-like functions accordingly.

To go further we could make sure they all follow similar semantics, i.e.:

• f(a) for the range from 0 included to a excluded
• f(a, b) for the range from a included to b excluded
• f(a, b, c) for the range from a included to b excluded, by steps of c

Functions in the global name space:

• ellipsis_range
• fibonacci_xrange
• mrange
• mrange_iter
• prime_range
• randrange
• range
• srange
• sxrange
• xmrange
• xmrange_iter
• xsrange

See also:

• prime_range should allow a step #29760: prime_range should allow a step
• Meta-ticket: improve compatibility with the Python library and Python packages #29728: Meta-ticket: improve compatibility with the Python library
• py3: need to fix sequence of ranges #24543: py3: need to fix sequence of ranges
• prime_range vs primes #18298: prime_range vs primes
• Add more examples for when srange is better than range #17373: Add more examples for when srange is better than range
• Deprecate sage.misc.mrange.*mrange* and cartesian_product_iterator #34337: Deprecate sage.misc.mrange.*mrange* and cartesian_product_iterator

CC: @slel @tscrim @fchapoton

Component: python3

Keywords: range

Branch/Commit: public/srange_as_iterator @ 3cee22e

Issue created by migration from https://trac.sagemath.org/ticket/30121

[slel]

comment:1

Initial list from a look at:

sage: [x for x in dir() if 'range' in x]

[mkoeppe]

comment:6

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

[fchapoton]

Branch: public/srange_as_iterator

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

efc3d67

make srange an iterator

[sagetrac-git]

Commit: efc3d67

[fchapoton]

comment:10

Making srange an iterator almost break every single file. Any volunteer to handle the fixes ?

[sagetrac-git]

Changed commit from efc3d67 to 3653098

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

3653098

one fix in plot

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

02df950

one more fix

[sagetrac-git]

Changed commit from 3653098 to 02df950

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

9eb53f6

more fixes for srange

[sagetrac-git]

Changed commit from 02df950 to 9eb53f6

[fchapoton]

comment:14

We meet the following issue:

sage: A = srange(1,4)                                                            
sage: list(A)                                                                   
[1, 2, 3]
sage: list(A)                                                                   
[]
sage: B = range(1,4)                                                              
sage: list(B)                                                                   
[1, 2, 3]
sage: list(B)                                                                   
[1, 2, 3]

[slel]

comment:15

According to the Python 3 documentation for range:

Rather than being a
function, range
is actually an immutable sequence type, as documented
in Ranges
and Sequence Types — list, tuple, range.

Could we make srange an immutable sequence type too?

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

9e33b25

make srange an iterator

[sagetrac-git]

Changed commit from 9eb53f6 to 9e33b25

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

b8740a6

using Iterable from collections.abc

[sagetrac-git]

Changed commit from 9e33b25 to b8740a6

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

6025e4d

one more fix for srange

[sagetrac-git]

Changed commit from b8740a6 to 6025e4d

[sagetrac-git]

Changed commit from 6025e4d to acd32da

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

acd32da

one more fix

[mkoeppe]

comment:20

I agree with comment:14 - this is problematic. srange should really construct an object similar to range objects in python3

[sagetrac-git]

Changed commit from acd32da to 4910cc6

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

4910cc6

make srange an iterator

[sagetrac-git]

Changed commit from 4910cc6 to 3cee22e

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

3cee22e

make srange an iterator

[mkoeppe]

comment:26

Can we just get rid of all *mrange* and replace its uses by itertools.product?
(I've opened #34337 for this.)

[tscrim]

comment:28

Replying to @mkoeppe:

Can we just get rid of all *mrange* and replace its uses by itertools.product?
(I've opened #34337 for this.)

I posted something on #34337 about somet hings to be careful about with doing the replacement.

[kedlaya]

I would suggest to add #31544 to the list of related issues.