Changes between Version 38 and Version 39 of Python3

Timestamp:

2020-10-15T13:45:15Z (5 years ago)

Author:

itamarst

Comment:

--

Python3

@@ -144 +144 @@
 
 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.
+
+== Dealing with utility modules ==
+
+Often you will have some utility module with lots of random code, some of which doesn't work on Python 3, or which even involves imports of non-Python-3-compatbile code (Nevow, in this case).
+
+Options:
+
+1. Create new `util_py3.py` module, move just the things you need, have `util.py` import code from there.
+2. Add conditional imports/declarations to `util.py` so it imports on Python 3 and at least some of the code can be made to work.
+
+Originally we went with first approach, but plausibly second approach is better.