Renames amqrpc backend to just 'rpc'

celery/backends/__init__.py

@@ -24,7 +24,7 @@ Unknown result backend: {0!r}.  Did you spell that correctly? ({1!r})\
 
 BACKEND_ALIASES = {
     'amqp': 'celery.backends.amqp:AMQPBackend',
-    'amqrpc': 'celery.backends.amqrpc.AMQRPCBackend',
+    'rpc': 'celery.backends.rpc.RPCBackend',
     'cache': 'celery.backends.cache:CacheBackend',
     'redis': 'celery.backends.redis:RedisBackend',
     'mongodb': 'celery.backends.mongodb:MongoBackend',

celery/backends/amqrpc.py → celery/backends/rpc.py

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 """
-    celery.backends.amqrpc
-    ~~~~~~~~~~~~~~~~~~~~~~
+    celery.backends.rpc
+    ~~~~~~~~~~~~~~~~~~~
 
     RPC-style result backend, using reply-to and one queue per client.
 
@@ -18,14 +18,14 @@ from celery import current_task
 from celery.backends import amqp
 
 
-class AMQRPCBackend(amqp.AMQPBackend):
+class RPCBackend(amqp.AMQPBackend):
     _tls = local()
 
     class Consumer(kombu.Consumer):
         auto_declare = False
 
     def _create_exchange(self, name, type='direct', persistent=False):
-        return self.Exchange('c.amqrpc', type=type, delivery_mode=1,
+        return self.Exchange('c.rep', type=type, delivery_mode=1,
                 durable=False, auto_delete=False)
 
     def on_task_call(self, producer, task_id):

docs/internals/reference/celery.backends.rpc.rst

@@ -0,0 +1,11 @@
+=======================================
+ celery.backends.rpc
+=======================================
+
+.. contents::
+    :local:
+.. currentmodule:: celery.backends.rpc
+
+.. automodule:: celery.backends.rpc
+    :members:
+    :undoc-members:

docs/internals/reference/index.rst

@@ -31,6 +31,7 @@
     celery.beat
     celery.backends
     celery.backends.base
+    celery.backends.rpc
     celery.backends.database
     celery.backends.cache
     celery.backends.amqp

docs/whatsnew-3.1.rst

@@ -172,7 +172,7 @@ In Other News
 
 
 
-- New result backend with RPC semantics (``amqrpc``).
+- New result backend with RPC semantics (``rpc``).
 
     This version of the ``amqp`` result backend is a very good alternative
     to use in classical RPC scenarios, where the process that initiates