Removes support for SQLAlchemy as a broker

README.rst

@@ -129,7 +129,7 @@ It supports...
     - **Message Transports**
 
         - RabbitMQ_, Redis_, Amazon SQS
-        - CouchDB_ (experimental), SQLAlchemy_ (experimental),
+        - CouchDB_ (experimental),
         - Django ORM (experimental), `IronMQ`_
         - and more...
 
@@ -311,8 +311,7 @@ Transports and Backends
     for using ZeroMQ as a message transport (*experimental*).
 
 :``celery[sqlalchemy]``:
-    for using SQLAlchemy as a message transport (*experimental*),
-    or as a result backend (*supported*).
+    for using SQLAlchemy as a result backend (*supported*).
 
 :``celery[pyro]``:
     for using the Pyro4 message transport (*experimental*).

docs/getting-started/brokers/index.rst

@@ -56,8 +56,6 @@ individual transport (see :ref:`broker_toc`).
 +---------------+--------------+----------------+--------------------+
 | *Django DB*   | Experimental | No             | No                 |
 +---------------+--------------+----------------+--------------------+
-| *SQLAlchemy*  | Experimental | No             | No                 |
-+---------------+--------------+----------------+--------------------+
 | *Iron MQ*     | third-party  | No             | No                 |
 +---------------+--------------+----------------+--------------------+
 

docs/getting-started/brokers/sqlalchemy.rst

@@ -1,77 +0,0 @@
-.. _broker-sqlalchemy:
-
-==================
- Using SQLAlchemy
-==================
-
-.. admonition:: Experimental Status
-
-    The SQLAlchemy transport is unstable in many areas and there are
-    several issues open.  Unfortunately we don't have the resources or funds
-    required to improve the situation, so we're looking for contributors
-    and partners willing to help.
-
-.. _broker-sqlalchemy-installation:
-
-Installation
-============
-
-.. _broker-sqlalchemy-configuration:
-
-Configuration
-=============
-
-Celery needs to know the location of your database, which should be the usual
-SQLAlchemy connection string, but with the ``sqla+`` prefix added:
-
-.. code-block:: python
-
-    broker_url = 'sqla+sqlite:///celerydb.sqlite'
-
-This transport uses only the :setting:`broker_url` setting, which have to be
-an SQLAlchemy database URI.
-
-
-Please see `SQLAlchemy: Supported Databases`_ for a table of supported databases.
-
-Here's a list of examples using a selection of other `SQLAlchemy Connection Strings`_:
-
-.. code-block:: python
-
-    # sqlite (filename)
-    broker_url = 'sqla+sqlite:///celerydb.sqlite'
-
-    # mysql
-    broker_url = 'sqla+mysql://scott:tiger@localhost/foo'
-
-    # postgresql
-    broker_url = 'sqla+postgresql://scott:tiger@localhost/mydatabase'
-
-    # oracle
-    broker_url = 'sqla+oracle://scott:tiger@127.0.0.1:1521/sidname'
-
-.. _`SQLAlchemy: Supported Databases`:
-    http://www.sqlalchemy.org/docs/core/engines.html#supported-databases
-
-.. _`SQLAlchemy Connection Strings`:
-    http://www.sqlalchemy.org/docs/core/engines.html#database-urls
-
-.. _sqlalchemy-results-configuration:
-
-Results
--------
-
-To store results in the database as well, you should configure the result
-backend.  See :ref:`conf-database-result-backend`.
-
-.. _broker-sqlalchemy-limitations:
-
-Limitations
-===========
-
-The SQLAlchemy database transport does not currently support:
-
-    * Remote control commands (:program:`celery events` command, broadcast)
-    * Events, including the Django Admin monitor.
-    * Using more than a few workers (can lead to messages being executed
-      multiple times).

docs/includes/installation.txt

@@ -105,8 +105,7 @@ Transports and Backends
     for using ZeroMQ as a message transport (*experimental*).
 
 :``celery[sqlalchemy]``:
-    for using SQLAlchemy as a message transport (*experimental*),
-    or as a result backend (*supported*).
+    for using SQLAlchemy as a result backend (*supported*).
 
 :``celery[pyro]``:
     for using the Pyro4 message transport (*experimental*).

docs/includes/introduction.txt

@@ -121,7 +121,7 @@ It supports…
     - **Message Transports**
 
         - RabbitMQ_, Redis_, Amazon SQS
-        - CouchDB_ (experimental), SQLAlchemy_ (experimental),
+        - CouchDB_ (experimental),
         - Django ORM (experimental), `IronMQ`_
         - and more…
 

docs/userguide/workers.rst

@@ -1008,8 +1008,7 @@ The output will include the following fields:
 
     * ``uri_prefix``
 
-        Some transports expects the host name to be a URL, this applies to
-        for example SQLAlchemy where the host name part is the connection URI:
+        Some transports expects the host name to be a URL.
 
         .. code-block:: text
 

requirements/extras/beanstalk.txt

@@ -1 +0,0 @@
-beanstalkc

requirements/extras/mongodb.txt

@@ -1 +0,0 @@
-pymongo>=2.6.2

setup.py

@@ -194,7 +194,7 @@ def extras(*p):
 features = set([
     'auth', 'cassandra', 'elasticsearch', 'memcache', 'pymemcache',
     'couchbase', 'threads', 'eventlet', 'gevent', 'msgpack', 'yaml',
-    'redis', 'mongodb', 'sqs', 'couchdb', 'riak', 'beanstalk', 'zookeeper',
+    'redis', 'sqs', 'couchdb', 'riak', 'zookeeper',
     'zeromq', 'sqlalchemy', 'librabbitmq', 'pyro', 'slmq', 'tblib', 'consul'
 ])
 extras_require = dict((x, extras(x + '.txt')) for x in features)