From bd3c3dd30dc74846c8327053e86a8d70f4da8e28 Mon Sep 17 00:00:00 2001
From: itamarst <>
Date: Thu, 15 Oct 2020 13:31:43 +0000
Subject: [PATCH] [Imported from Trac: page Python3, version 38]

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

diff --git a/Python3.md b/Python3.md
index 801e875..366530e 100644
--- a/Python3.md
+++ b/Python3.md
@@ -88,6 +88,8 @@ As the port progresses, the simple "port module + its test module" gets difficul
 1. Port *only* the test module. This involves many Python 3 fixes to lots of other modules, but they are not officially ported, they're just inched along just enough to make the tests pass. Since the test module is officially ported, regressions to the Python 3 port still are prevented.
 2. Then, port the corresponding module.
 
+When doing the incidental fixes to other modules, try to change as little as possible: no `*future*` imports, no `from future.builtins import all thte things`, just enough changes to make the tests you care enough pass. This reduces chances of unintentional breakage and unintentional scope creep. You might even do temporary things like `from past.builtins import unicode`. Later on when specifically porting a you can Do All The Things the right way.
+
 ### Porting a specific Python file
 
 **Zeroth**, file a new ticket in milestone "Python 3", assign it to yourself.