From c579f27f6d588cca2629974ddcb7af461b1226c7 Mon Sep 17 00:00:00 2001 From: Benjamin Bach Date: Thu, 28 Apr 2016 18:13:12 +0200 Subject: [PATCH] Update to clarify Python Compatibility (#140) Does this make sense? A fellow team member didn't believe that Channels were Python 3 ready after looking at the docs, so I though it's best to clarify it once and for all, for instance in the FAQ? --- docs/faqs.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/faqs.rst b/docs/faqs.rst index e4250e5..08482c0 100755 --- a/docs/faqs.rst +++ b/docs/faqs.rst @@ -125,3 +125,11 @@ which is the unique channel representing the connection, but remember that whatever you store in must be **network-transparent** - storing things in a global variable won't work outside of development. + + +Are channels Python 2, 3 or 2+3? +-------------------------------- + +Django-channels and all of its dependencies are 2+3 (2.7, 3.4+). Compatibility may change with time. If in doubt, refer to the ``.travis.yml`` configuration file to see which Python versions that are included in CI testing. + +This includes Twisted, for which the used subsets of the library used by Daphne are all py3k ready.