[Python-modules-commits] r14850 - in trunk/celery/debian/patches (debian-changes-2.1.2-1 series)
statik-guest at users.alioth.debian.org
statik-guest at users.alioth.debian.org
Sat Nov 6 00:52:51 UTC 2010
Date: Saturday, November 6, 2010 @ 00:52:34
Author: statik-guest
Revision: 14850
Unwanted patch.
Modified:
trunk/celery/debian/patches/series
Deleted:
trunk/celery/debian/patches/debian-changes-2.1.2-1
Deleted: trunk/celery/debian/patches/debian-changes-2.1.2-1
===================================================================
--- trunk/celery/debian/patches/debian-changes-2.1.2-1 2010-11-06 00:49:09 UTC (rev 14849)
+++ trunk/celery/debian/patches/debian-changes-2.1.2-1 2010-11-06 00:52:34 UTC (rev 14850)
@@ -1,306 +0,0 @@
-Description: Upstream changes introduced in version 2.1.2-1
- This patch has been created by dpkg-source during the package build.
- Here's the last changelog entry, hopefully it gives details on why
- those changes were made:
- .
- celery (2.1.2-1) UNRELEASED; urgency=low
- .
- * Initial release (Closes: #526350)
- .
- The person named in the Author field signed this changelog entry.
-Author: Elliot Murphy <elliot at ubuntu.com>
-Bug-Debian: http://bugs.debian.org/526350
-
----
-The information above should follow the Patch Tagging Guidelines, please
-checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
-are templates for supplementary fields that you might want to add:
-
-Origin: <vendor|upstream|other>, <url of original patch>
-Bug: <url in upstream bugtracker>
-Bug-Debian: http://bugs.debian.org/<bugnumber>
-Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
-Forwarded: <no|not-needed|url proving that it has been forwarded>
-Reviewed-By: <name and email of someone who approved the patch>
-Last-Update: <YYYY-MM-DD>
-
---- celery-2.1.2.orig/celery.egg-info/PKG-INFO
-+++ celery-2.1.2/celery.egg-info/PKG-INFO
-@@ -7,7 +7,7 @@ Author: Ask Solem
- Author-email: ask at celeryproject.org
- License: BSD
- Description: =================================
-- celery - Distributed Task Queue
-+ celery - Distributed Task Queue
- =================================
-
- .. image:: http://cloud.github.com/downloads/ask/celery/celery_favicon_128.png
-@@ -17,7 +17,7 @@ Description: ===========================
- :Download: http://pypi.python.org/pypi/celery/
- :Source: http://github.com/ask/celery/
- :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis,
-- python, webhooks, queue, distributed
-+ python, webhooks, queue, distributed
-
- --
-
-@@ -52,10 +52,10 @@ Description: ===========================
- .. _`celery-pylons`: http://pypi.python.org/pypi/celery-pylons
- .. _`Flask-Celery`: http://github.com/ask/flask-celery/
- .. _`operate with other languages using webhooks`:
-- http://ask.github.com/celery/userguide/remote-tasks.html
-+ http://ask.github.com/celery/userguide/remote-tasks.html
-
- .. contents::
-- :local:
-+ :local:
-
- .. _celery-overview:
-
-@@ -82,17 +82,17 @@ Description: ===========================
- adding two numbers:
- ::
-
-- from celery.decorators import task
-+ from celery.decorators import task
-
-- @task
-- def add(x, y):
-- return x + y
-+ @task
-+ def add(x, y):
-+ return x + y
-
- You can execute the task in the background, or wait for it to finish::
-
-- >>> result = add.delay(4, 4)
-- >>> result.wait() # wait for and return the result
-- 8
-+ >>> result = add.delay(4, 4)
-+ >>> result.wait() # wait for and return the result
-+ 8
-
- Simple!
-
-@@ -101,84 +101,84 @@ Description: ===========================
- Features
- ========
-
-- +-----------------+----------------------------------------------------+
-- | Messaging | Supported brokers include `RabbitMQ`_, `Stomp`_, |
-- | | `Redis`_, and most common SQL databases. |
-- +-----------------+----------------------------------------------------+
-- | Robust | Using `RabbitMQ`, celery survives most error |
-- | | scenarios, and your tasks will never be lost. |
-- +-----------------+----------------------------------------------------+
-- | Distributed | Runs on one or more machines. Supports |
-- | | `clustering`_ when used in combination with |
-- | | `RabbitMQ`_. You can set up new workers without |
-- | | central configuration (e.g. use your dads laptop |
-- | | while the queue is temporarily overloaded). |
-- +-----------------+----------------------------------------------------+
-- | Concurrency | Tasks are executed in parallel using the |
-- | | ``multiprocessing`` module. |
-- +-----------------+----------------------------------------------------+
-- | Scheduling | Supports recurring tasks like cron, or specifying |
-- | | an exact date or countdown for when after the task |
-- | | should be executed. |
-- +-----------------+----------------------------------------------------+
-- | Performance | Able to execute tasks while the user waits. |
-- +-----------------+----------------------------------------------------+
-- | Return Values | Task return values can be saved to the selected |
-- | | result store backend. You can wait for the result, |
-- | | retrieve it later, or ignore it. |
-- +-----------------+----------------------------------------------------+
-- | Result Stores | Database, `MongoDB`_, `Redis`_, `Tokyo Tyrant`, |
-- | | `AMQP`_ (high performance). |
-- +-----------------+----------------------------------------------------+
-- | Webhooks | Your tasks can also be HTTP callbacks, enabling |
-- | | cross-language communication. |
-- +-----------------+----------------------------------------------------+
-- | Rate limiting | Supports rate limiting by using the token bucket |
-- | | algorithm, which accounts for bursts of traffic. |
-- | | Rate limits can be set for each task type, or |
-- | | globally for all. |
-- +-----------------+----------------------------------------------------+
-- | Routing | Using AMQP you can route tasks arbitrarily to |
-- | | different workers. |
-- +-----------------+----------------------------------------------------+
-- | Remote-control | You can rate limit and delete (revoke) tasks |
-- | | remotely. |
-- +-----------------+----------------------------------------------------+
-- | Monitoring | You can capture everything happening with the |
-- | | workers in real-time by subscribing to events. |
-- | | A real-time web monitor is in development. |
-- +-----------------+----------------------------------------------------+
-- | Serialization | Supports Pickle, JSON, YAML, or easily defined |
-- | | custom schemes. One task invocation can have a |
-- | | different scheme than another. |
-- +-----------------+----------------------------------------------------+
-- | Tracebacks | Errors and tracebacks are stored and can be |
-- | | investigated after the fact. |
-- +-----------------+----------------------------------------------------+
-- | UUID | Every task has an UUID (Universally Unique |
-- | | Identifier), which is the task id used to query |
-- | | task status and return value. |
-- +-----------------+----------------------------------------------------+
-- | Retries | Tasks can be retried if they fail, with |
-- | | configurable maximum number of retries, and delays |
-- | | between each retry. |
-- +-----------------+----------------------------------------------------+
-- | Task Sets | A Task set is a task consisting of several |
-- | | sub-tasks. You can find out how many, or if all |
-- | | of the sub-tasks has been executed, and even |
-- | | retrieve the results in order. Progress bars, |
-- | | anyone? |
-- +-----------------+----------------------------------------------------+
-- | Made for Web | You can query status and results via URLs, |
-- | | enabling the ability to poll task status using |
-- | | Ajax. |
-- +-----------------+----------------------------------------------------+
-- | Error e-mails | Can be configured to send e-mails to the |
-- | | administrators when tasks fails. |
-- +-----------------+----------------------------------------------------+
-- | Supervised | Pool workers are supervised and automatically |
-- | | replaced if they crash. |
-- +-----------------+----------------------------------------------------+
-+ +-----------------+----------------------------------------------------+
-+ | Messaging | Supported brokers include `RabbitMQ`_, `Stomp`_, |
-+ | | `Redis`_, and most common SQL databases. |
-+ +-----------------+----------------------------------------------------+
-+ | Robust | Using `RabbitMQ`, celery survives most error |
-+ | | scenarios, and your tasks will never be lost. |
-+ +-----------------+----------------------------------------------------+
-+ | Distributed | Runs on one or more machines. Supports |
-+ | | `clustering`_ when used in combination with |
-+ | | `RabbitMQ`_. You can set up new workers without |
-+ | | central configuration (e.g. use your dads laptop |
-+ | | while the queue is temporarily overloaded). |
-+ +-----------------+----------------------------------------------------+
-+ | Concurrency | Tasks are executed in parallel using the |
-+ | | ``multiprocessing`` module. |
-+ +-----------------+----------------------------------------------------+
-+ | Scheduling | Supports recurring tasks like cron, or specifying |
-+ | | an exact date or countdown for when after the task |
-+ | | should be executed. |
-+ +-----------------+----------------------------------------------------+
-+ | Performance | Able to execute tasks while the user waits. |
-+ +-----------------+----------------------------------------------------+
-+ | Return Values | Task return values can be saved to the selected |
-+ | | result store backend. You can wait for the result, |
-+ | | retrieve it later, or ignore it. |
-+ +-----------------+----------------------------------------------------+
-+ | Result Stores | Database, `MongoDB`_, `Redis`_, `Tokyo Tyrant`, |
-+ | | `AMQP`_ (high performance). |
-+ +-----------------+----------------------------------------------------+
-+ | Webhooks | Your tasks can also be HTTP callbacks, enabling |
-+ | | cross-language communication. |
-+ +-----------------+----------------------------------------------------+
-+ | Rate limiting | Supports rate limiting by using the token bucket |
-+ | | algorithm, which accounts for bursts of traffic. |
-+ | | Rate limits can be set for each task type, or |
-+ | | globally for all. |
-+ +-----------------+----------------------------------------------------+
-+ | Routing | Using AMQP you can route tasks arbitrarily to |
-+ | | different workers. |
-+ +-----------------+----------------------------------------------------+
-+ | Remote-control | You can rate limit and delete (revoke) tasks |
-+ | | remotely. |
-+ +-----------------+----------------------------------------------------+
-+ | Monitoring | You can capture everything happening with the |
-+ | | workers in real-time by subscribing to events. |
-+ | | A real-time web monitor is in development. |
-+ +-----------------+----------------------------------------------------+
-+ | Serialization | Supports Pickle, JSON, YAML, or easily defined |
-+ | | custom schemes. One task invocation can have a |
-+ | | different scheme than another. |
-+ +-----------------+----------------------------------------------------+
-+ | Tracebacks | Errors and tracebacks are stored and can be |
-+ | | investigated after the fact. |
-+ +-----------------+----------------------------------------------------+
-+ | UUID | Every task has an UUID (Universally Unique |
-+ | | Identifier), which is the task id used to query |
-+ | | task status and return value. |
-+ +-----------------+----------------------------------------------------+
-+ | Retries | Tasks can be retried if they fail, with |
-+ | | configurable maximum number of retries, and delays |
-+ | | between each retry. |
-+ +-----------------+----------------------------------------------------+
-+ | Task Sets | A Task set is a task consisting of several |
-+ | | sub-tasks. You can find out how many, or if all |
-+ | | of the sub-tasks has been executed, and even |
-+ | | retrieve the results in order. Progress bars, |
-+ | | anyone? |
-+ +-----------------+----------------------------------------------------+
-+ | Made for Web | You can query status and results via URLs, |
-+ | | enabling the ability to poll task status using |
-+ | | Ajax. |
-+ +-----------------+----------------------------------------------------+
-+ | Error e-mails | Can be configured to send e-mails to the |
-+ | | administrators when tasks fails. |
-+ +-----------------+----------------------------------------------------+
-+ | Supervised | Pool workers are supervised and automatically |
-+ | | replaced if they crash. |
-+ +-----------------+----------------------------------------------------+
-
-
- .. _`clustering`: http://www.rabbitmq.com/clustering.html
-@@ -207,11 +207,11 @@ Description: ===========================
-
- To install using ``pip``,::
-
-- $ pip install celery
-+ $ pip install celery
-
- To install using ``easy_install``,::
-
-- $ easy_install celery
-+ $ easy_install celery
-
- .. _celery-installing-from-source:
-
-@@ -223,10 +223,10 @@ Description: ===========================
-
- You can install it by doing the following,::
-
-- $ tar xvfz celery-0.0.0.tar.gz
-- $ cd celery-0.0.0
-- $ python setup.py build
-- # python setup.py install # as root
-+ $ tar xvfz celery-0.0.0.tar.gz
-+ $ cd celery-0.0.0
-+ $ python setup.py build
-+ # python setup.py install # as root
-
- .. _celery-installing-from-git:
-
-@@ -235,7 +235,7 @@ Description: ===========================
-
- You can clone the repository by doing the following::
-
-- $ git clone git://github.com/ask/celery.git
-+ $ git clone git://github.com/ask/celery.git
-
- .. _getting-help:
-
-@@ -248,7 +248,7 @@ Description: ===========================
- ------------
-
- For discussions about the usage, development, and future of celery,
-- please join the `celery-users`_ mailing list.
-+ please join the `celery-users`_ mailing list.
-
- .. _`celery-users`: http://groups.google.com/group/celery-users/
-
---- celery-2.1.2.orig/celery.egg-info/requires.txt
-+++ celery-2.1.2/celery.egg-info/requires.txt
-@@ -1,5 +1,5 @@
-+importlib
- python-dateutil
- anyjson
- carrot>=0.10.7
--pyparsing
--multiprocessing
-\ No newline at end of file
-+pyparsing
-\ No newline at end of file
Modified: trunk/celery/debian/patches/series
===================================================================
--- trunk/celery/debian/patches/series 2010-11-06 00:49:09 UTC (rev 14849)
+++ trunk/celery/debian/patches/series 2010-11-06 00:52:34 UTC (rev 14850)
@@ -1 +0,0 @@
-debian-changes-2.1.2-1
More information about the Python-modules-commits
mailing list