From 0bfdfb8e55a214976d01f29c997dd72f2ee266d6 Mon Sep 17 00:00:00 2001
From: itamarst <>
Date: Wed, 5 Aug 2020 15:49:18 +0000
Subject: [PATCH] [Imported from Trac: page Python3, version 14]

---
 Python3.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Python3.md b/Python3.md
index 2091e92..c5f123d 100644
--- a/Python3.md
+++ b/Python3.md
@@ -58,7 +58,7 @@ And replace the `from builtins import *` variant, if any, with:
 ```#!python
 from future.utils import PY2
 if PY2:
-    from future.builtins import filter, map, zip, ascii, chr, hex, input, next, oct, open, pow, round, super, bytes, dict, int, list, object, range, str, max, min  # noqa: F401
+    from future.builtins import filter, map, zip, ascii, chr, hex, input, next, oct, open, pow, round, super, bytes, dict, list, object, range, str, max, min  # noqa: F401
 ```
 
 ### When things get complicated
@@ -94,7 +94,7 @@ One of them is the `bytes` objects:
 
 ## Don't leak Future objects
 
-Leaking Future objects (newints, new dicts, new bytes) in module API can break existing code on Python 2. So need to be careful not to do that. For that reason int isn't in the suggested list above.
+Leaking Future objects (newints, new dicts, new bytes) in module API can break existing code on Python 2. So need to be careful not to do that. For that reason int isn't in the suggested `from builtins import ...` list above.
 
 ## Other notes