py3 get rid of xrange in graphs folder

[fchapoton]

using instead six.moves.range

only in .py files

CC: @tscrim @jm58660 @a-andre @jdemeyer

Component: python3

Author: Frédéric Chapoton

Branch/Commit: 4ff72b5

Reviewer: Jori Mäntysalo

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

[fchapoton]

New commits:

631989b

get rid of xrange in graph folder

[fchapoton]

Branch: u/chapoton/21530

[fchapoton]

Commit: 631989b

[fchapoton]

comment:2

green bot

[jm58660]

Reviewer: Jori Mäntysalo

[jm58660]

comment:4

Works.

[-2*t+i for i in range(2*t)] is not beatiful.

It is not needed to change g.add_vertices(range(11)), as add_vertices() can take an iterator. (Same does not apply to add_cycle(), but maybe it should.

What is the meaning of new_verts = [self.add_vertex() for i in range(k)]? add_vertex() has no return value.

list(range(20))[10:20] is odd.

Feel free to mark this as positive review without any changes, as this patch does not make any of those worst than they now are.

[sagetrac-git]

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

4ff72b5

trac 21530 some details, plus a few ....:

[sagetrac-git]

Changed commit from 631989b to 4ff72b5

[fchapoton]

comment:6

ok, done. It seems that add_vertex sometimes return the number of the new vertex.

[jm58660]

comment:7

Replying to @fchapoton:

ok, done.

OK. --> positive_review.

It seems that add_vertex sometimes return the number of the new vertex.

I didn't notice that.

[vbraun]

Changed branch from u/chapoton/21530 to 4ff72b5