doctest Python vs Sage ints

[vbraun]

This patch changes how the display manager pretty-prints plain Python integers:

sage: 1
1
sage: int(2)
int(2)
sage: len(['a', 'b', 'c'])
int(3)
sage: Set(['a', 'b', 'c', 'd']).cardinality()
4

CC: @nathanncohen @jm58660

Component: user interface

Branch/Commit: u/vbraun/doctest_python_vs_sage_ints @ 129259d

Reviewer: Jeroen Demeyer, Volker Braun

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

[vbraun]

Branch: u/vbraun/doctest_python_vs_sage_ints

[vbraun]

Description changed:

--- 
+++ 
@@ -1 +1,12 @@
+This patch changes how the display manager pretty-prints plain Python integers:
 
+```
+sage: 1
+1
+sage: int(2)
+int(2)
+sage: len(['a', 'b', 'c'])
+int(3)
+sage: Set(['a', 'b', 'c', 'd']).cardinality()
+4
+```

[vbraun]

Author: Volker Braun

[vbraun]

New commits:

fc16fc0

Distinguish Python integers from Sage integers

[vbraun]

Commit: fc16fc0

[sagetrac-jkeitel]

comment:4

This includes Booleans at the moment:

sage: True, False
(int(True), int(False))

[videlec]

comment:5

Replying to @sagetrac-jkeitel:

This includes Booleans at the moment:

sage: True, False
(int(True), int(False))

Yep. bool is a subtype of int. One should replace isinstance(obj, int) with type(obj) is int.

[sagetrac-git]

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

c7d5312

match int type exactly

[sagetrac-git]

Changed commit from fc16fc0 to c7d5312

[sagetrac-git]

Changed commit from c7d5312 to 129259d

[sagetrac-git]

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

129259d

fix the implicit sig_on_count doctest