summaryrefslogtreecommitdiff
path: root/doc/python3.rst
diff options
context:
space:
mode:
authorOlivier Dony <odo@openerp.com>2017-09-15 16:50:09 +0200
committerOlivier Dony <odo@openerp.com>2017-09-15 16:51:47 +0200
commit35e80c1ab5c641135c9ff190bbf2b8aca7e33a1d (patch)
tree49599317efadddabd167ac222c5278b7d9414fa3 /doc/python3.rst
parentabc1f0b30555b57b899a52054e271a022cd41d9f (diff)
[IMP] doc: update P3 compatibility policy
Diffstat (limited to 'doc/python3.rst')
-rw-r--r--doc/python3.rst13
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/python3.rst b/doc/python3.rst
index c8e8269936e..dc063c2b145 100644
--- a/doc/python3.rst
+++ b/doc/python3.rst
@@ -4,9 +4,16 @@
Python 3 compatibility/conversions
==================================
-Goal (notsure?): for v11 to provide an alpha/beta Python 3 compatibility, for
-v12 to provide official Python 3 support and drop Python 2 in either v12 or
-v13.
+Official compatibility: Odoo 11 will be the first LTS release to introduce
+Python 3 compatibility, starting with Python 3.5. It will also be the first
+LTS release to drop official support for Python 2.
+
+Rationale: Python 3 has been around since 2008, and all Python libraries
+used by the official Odoo distribution have been ported and are considered
+stable. Most supported platforms have a Python 3.5 package, or a similar
+way to deploy it. Preserving dual compatibility is therefore considered
+unnecessary, and would represent a significant overhead in testing for the
+lifetime of Odoo 11.
Python 2 and Python 3 are somewhat different language, but following
backports, forward ports and cross-compatibility library it is possible to