From ecb2e4c22b80100637197e77f192a53e62f10681 Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Fri, 18 Dec 2015 21:34:47 +0000 Subject: [PATCH] Remove old note --- docs/integration-changes.rst | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/integration-changes.rst b/docs/integration-changes.rst index c59fa38..7fa5c6e 100644 --- a/docs/integration-changes.rst +++ b/docs/integration-changes.rst @@ -4,8 +4,7 @@ Integration Notes Django Channels is intended to be merged into Django itself; these are the planned changes the codebase will need to undertake in that transition. -* The ``channels`` package will become ``django.channels``. The expected way - of interacting with the system will be via the ``Channel`` object, +* The ``channels`` package will become ``django.channels``, and main objects will keep their import path. * Obviously, the monkeypatches in ``channels.hacks`` will be replaced by placing methods onto the objects themselves. The ``request`` and ``response`` @@ -17,8 +16,3 @@ Things to ponder * The mismatch between signals (broadcast) and channels (single-worker) means we should probably leave patching signals into channels for the end developer. This would also ensure the speedup improvements for empty signals keep working. - -* It's likely that the decorator-based approach of consumer registration will - mean extending Django's auto-module-loading beyond ``models`` and - ``admin`` app modules to include ``views`` and ``consumers``. There may be - a better unified approach to this.