Browse Source

Celery 5 will depend on Python 3.5, as this is the target for pypy

Ask Solem 8 years ago
parent
commit
1c6f00050d
4 changed files with 5 additions and 5 deletions
  1. 1 1
      README.rst
  2. 1 1
      docs/getting-started/introduction.rst
  3. 1 1
      docs/includes/introduction.txt
  4. 2 2
      docs/whatsnew-4.0.rst

+ 1 - 1
README.rst

@@ -53,7 +53,7 @@ Celery version 4.0 runs on,
 
 
 This is the last version to support Python 2.7,
-and from the next version (Celery 5.x) Python 3.6 or newer is required.
+and from the next version (Celery 5.x) Python 3.5 or newer is required.
 
 If you're running an older version of Python, you need to be running
 an older version of Celery:

+ 1 - 1
docs/getting-started/introduction.rst

@@ -44,7 +44,7 @@ What do I need?
     - PyPy ❨5.1, 2.4❩
 
     This is the last version to support Python 2.7,
-    and from the next version (Celery 5.x) Python 3.6 or newer is required.
+    and from the next version (Celery 5.x) Python 3.5 or newer is required.
 
     If you're running an older version of Python, you need to be running
     an older version of Celery:

+ 1 - 1
docs/includes/introduction.txt

@@ -45,7 +45,7 @@ Celery version 4.0 runs on,
 
 
 This is the last version to support Python 2.7,
-and from the next version (Celery 5.x) Python 3.6 or newer is required.
+and from the next version (Celery 5.x) Python 3.5 or newer is required.
 
 If you're running an older version of Python, you need to be running
 an older version of Celery:

+ 2 - 2
docs/whatsnew-4.0.rst

@@ -110,14 +110,14 @@ and also drops support for Python 3.3 so supported versions are:
 Last major version to support Python 2
 --------------------------------------
 
-Starting from Celery 5.0 only Python 3.6+ will be supported.
+Starting from Celery 5.0 only Python 3.5+ will be supported.
 
 To make sure you're not affected by this change you should pin
 the Celery version in your requirements file, either to a specific
 version: ``celery==4.0.0``, or a range: ``celery>=4.0,<5.0``.
 
 Dropping support for Python 2 will enable us to remove massive
-amounts of compatibility code, and going with Python 3.6 allows
+amounts of compatibility code, and going with Python 3.5 allows
 us to take advantage of typing, async/await, asyncio, and similar
 concepts there's no alternative for in older versions.