diff options
| author | Simon McVittie <smcv@debian.org> | 2016-08-11 10:15:01 +0100 |
|---|---|---|
| committer | Simon McVittie <smcv@debian.org> | 2016-08-11 10:15:01 +0100 |
| commit | 167200cef749be40b3d3624cfb86a5928aeca522 (patch) | |
| tree | 6fa3088bcbb0982acfe5cb179b4b85870c79bbd8 /doc | |
| parent | 1013581fef91c9be087d6264084cec34c2ca6e9a (diff) | |
Drop support for Python 2.6, along with several workarounds
It hasn't had security support for about 3 years.
Signed-off-by: Simon McVittie <smcv@debian.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/PY3PORT.txt | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/PY3PORT.txt b/doc/PY3PORT.txt index 31bb9d8..a028153 100644 --- a/doc/PY3PORT.txt +++ b/doc/PY3PORT.txt @@ -34,7 +34,7 @@ You've got some dbus-python code that works great in Python 2. This branch should generally allow your existing Python 2 code to continue to work unchanged. There are a few changes you'll notice in Python 2 though: - - The minimum supported Python 2 version is 2.6. + - The minimum supported Python 2 version is 2.7. - All object reprs are unicodes. This change was made because it greatly simplifies the implementation and cross-compatibility with Python 3. - Some exception strings have changed. @@ -209,8 +209,6 @@ any return path. - `isSequenceType()` is gone in Python 3, so I use a different idiom there. - `__next__()` vs. `next()` - `PyUnicode_FromFormat()` `%V` flag is a clever hack! - - `sys.version_info` is a tuple in Python 2.6, not a namedtuple. i.e. there - is no `sys.version_info.major` - `PyArg_Parse()`: No 'y' code in Python 2; in Python 3, no equivalent of 'z' for bytes objects. |