moved some docs of the BusABC to the development section

felixdivo · felixdivo · commit 6a527fb2b7c9 · 2018-05-28T00:51:27.000+02:00
diff --git a/can/bus.py b/can/bus.py
@@ -51,14 +51,6 @@ def __str__(self):
     def recv(self, timeout=None):
         """Block waiting for a message from the Bus.
 
-        If the concrete bus does not override it, this method makes sure
-        that all filters have been applied. That is the case for all
-        internal interfaces.
-
-        To enable receiving for an interface, please override
-        :meth:`~can.BusABC._recv_internal` instead of this one.
-        Overriding this method is deprecated.
-
         :param float timeout:
             seconds to wait for a message or None to wait indefinitely
 
diff --git a/doc/development.rst b/doc/development.rst
@@ -48,7 +48,7 @@ About the ``BusABC`` class
 Concrete implementations *have to* implement the following:
     * :meth:`~can.BusABC.send` to send individual messages
     * :meth:`~can.BusABC._recv_internal` to receive individual messages
-      (see note below)
+      (see note below!)
     * set the :attr:`~can.BusABC.channel_info` attribute to a string describing
       the underlying bus and/or channel
 
@@ -69,11 +69,15 @@ They *might* implement the following:
 
 .. note::
 
+    *TL;DR*: Only override :meth:`~can.BusABC._recv_internal`,
+    never :meth:`~can.BusABC.recv` directly.
+
     Previously, concrete bus classes had to override :meth:`~can.BusABC.recv`
     directly instead of :meth:`~can.BusABC._recv_internal`, but that has
     changed to allow the abstract base class to handle in-software message
-    filtering as a fallback. Older (custom) interfaces might still be
-    implemented like that and thus might not provide message filtering.
+    filtering as a fallback. All internal interfaces now implement that new
+    behaviour. Older (custom) interfaces might still be implemented like that
+    and thus might not provide message filtering:
 
 
 Creating a Release
