Partially replace "<type" by "<class" in src/sage

[fchapoton]

moving away from python2

Done using several bash commands like

grep -rl " <type " src/sage/modular/ | xargs sed -i 's/<type/<class/g'

Component: refactoring

Author: Frédéric Chapoton

Branch/Commit: 471b52f

Reviewer: Kwankyu Lee

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

[fchapoton]

New commits:

46cf067

convert some

[fchapoton]

Commit: 46cf067

[fchapoton]

Description changed:

--- 
+++ 
@@ -1 +1,7 @@
 moving away from python2
+
+Done using several bash commands like
+
+```
+grep -rl " <type " src/sage/modular/ | xargs sed -i 's/<type/<class/g'
+```

[fchapoton]

Branch: u/chapoton/32675

[kwankyu]

comment:2

The bot failure is genuine.

Question: why not fix all and remove the related python2 normalizer in the doctest framework?

[fchapoton]

comment:3

Replying to @kwankyu:

The bot failure is genuine.

no idea how change in the doc could trigger such a build failure..

Question: why not fix all and remove the related python2 normalizer in the doctest framework?

Well, this is the aim but one must first fix many doctests.

[kwankyu]

comment:4

Replying to @fchapoton:

Replying to @kwankyu:

The bot failure is genuine.

no idea how change in the doc could trigger such a build failure..

There is a change out of the doc.

Question: why not fix all and remove the related python2 normalizer in the doctest framework?

Well, this is the aim but one must first fix many doctests.

Which is the case (1) you are not sure of having fixed all or (2) there are parts of sage lib that you didn't touch yet?

[sagetrac-git]

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

471b52f

fix wrong change

[sagetrac-git]

Changed commit from 46cf067 to 471b52f

[fchapoton]

comment:6

Replying to @kwankyu:

Replying to @fchapoton:

Replying to @kwankyu:

The bot failure is genuine.

no idea how change in the doc could trigger such a build failure..

There is a change out of the doc.

Indeed, I have found it now.

Question: why not fix all and remove the related python2 normalizer in the doctest framework?

Well, this is the aim but one must first fix many doctests.

Which is the case (1) you are not sure of having fixed all or (2) there are parts of sage lib that you didn't touch yet?

The situation is (2). For example the rings/ folder.