Hello community, here is the log from the commit of package python-celery for openSUSE:Factory checked in at 2012-10-07 19:55:14 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-celery (Old) and /work/SRC/openSUSE:Factory/.python-celery.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-celery", Maintainer is "" Changes: -------- --- /work/SRC/openSUSE:Factory/python-celery/python-celery.changes 2012-09-14 12:34:28.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python-celery.new/python-celery.changes 2012-10-07 19:55:16.000000000 +0200 @@ -1,0 +2,156 @@ +Wed Sep 26 17:42:49 UTC 2012 - [email protected] + +- Update to 3.0.11: + - generic-init.d scripts changed permissions of /var/log & /var/run + In the daemonization tutorial the recommended directories were as follows: + + CELERYD_LOG_FILE="/var/log/celery/%n.log" + CELERYD_PID_FILE="/var/run/celery/%n.pid" + + But in the scripts themselves the default files were /var/log/celery%n.log + and /var/run/celery%n.pid, so if the user did not change the location + by configuration, the directories /var/log and /var/run would be + created - and worse have their permissions and owners changed. + + This change means that: + + - Default pid file is /var/run/celery/%n.pid + - Default log file is /var/log/celery/%n.log + + - The directories are only created and have their permissions + changed if *no custom locations are set*. + + Users can force paths to be created by calling the create-paths + subcommand: + + $ sudo /etc/init.d/celeryd create-paths + + Upgrading Celery will not update init scripts + + To update the init scripts you have to re-download + the files from source control and update them manually. + You can find the init scripts for version 3.0.x at: + + http://github.com/celery/celery/tree/3.0/extra/generic-init.d + + - Now depends on billiard 2.7.3.17 + - Fixes request stack protection when app is initialized more than + once (Issue #1003). + - ETA tasks now properly works when system timezone is not the same + as the configured timezone (Issue #1004). + - Terminating a task now works if the task has been sent to the + pool but not yet acknowledged by a pool process (Issue #1007). + + Fix contributed by Alexey Zatelepin + - Terminating a task now properly updates the state of the task to revoked, + and sends a ``task-revoked`` event. + - Multi: No longer parses --app option (Issue #1008). + - Generic worker init script now waits for workers to shutdown by default. + - Multi: stop_verify command renamed to stopwait. + - Daemonization: Now delays trying to create pidfile/logfile until after + the working directory has been changed into. + - celery worker and celery beat commands now respects + the --no-color option (Issue #999). + - Fixed typos in eventlet examples (Issue #1000) + + Fix contributed by Bryan Bishop. + Congratulations on opening bug #1000! + - Tasks that raise celery.exceptions.Ignore are now acknowledged. + - Beat: Now shows the name of the entry in sending due task logs. + + +------------------------------------------------------------------- +Thu Sep 20 22:24:32 UTC 2012 - [email protected] + +- Update to 3.0.10: + - Now depends on kombu 2.4.7 + - Now depends on billiard 2.7.3.14 + - Fixes crash at startup when using Django and pre-1.4 projects + (setup_environ). + - Hard time limits now sends the KILL signal shortly after TERM, + to terminate processes that have signal handlers blocked by C extensions. + - Billiard now installs even if the C extension cannot be built. + It's still recommended to build the C extension if you are using + a transport other than rabbitmq/redis (or use forced execv for some + other reason). + - Pool now sets a ``current_process().index`` attribute that can be used to create + as many log files as there are processes in the pool. + - Canvas: chord/group/chain no longer modifies the state when called + Previously calling a chord/group/chain would modify the ids of subtasks + so that: + + >>> c = chord([add.s(2, 2), add.s(4, 4)], xsum.s()) + >>> c() + >>> c() <-- call again + + at the second time the ids for the tasks would be the same as in the + previous invocation. This is now fixed, so that calling a subtask + won't mutate any options. + - Canvas: Chaining a chord to another task now works (Issue #965). + - Worker: Fixed a bug where the request stack could be corrupted if + relative imports are used. + + Problem usually manifested itself as an exception while trying to + send a failed task result (NoneType does not have id attribute). + + Fix contributed by Sam Cooke. + - Tasks can now raise celery.exceptions.Ignore to skip updating states + or events after return. + + Example: + + from celery.exceptions import Ignore + + @task + def custom_revokes(): + if redis.sismember('tasks.revoked', custom_revokes.request.id): + raise Ignore() + + - The worker now makes sure the request/task stacks are not modified + by the initial Task.__call__. + + This would previously be a problem if a custom task class defined + __call__ and also called super(). + - Because of problems the fast local optimization has been disabled, + and can only be enabled by setting the USE_FAST_LOCALS attribute. + - Worker: Now sets a default socket timeout of 5 seconds at shutdown + so that broken socket reads do not hinder proper shutdown (Issue #975). + - More fixes related to late eventlet/gevent patching. + - Documentation for settings out of sync with reality: + + - CELERY_TASK_PUBLISH_RETRY + + Documented as disabled by default, but it was enabled by default + since 2.5 as stated by the 2.5 changelog. + + - CELERY_TASK_PUBLISH_RETRY_POLICY + + The default max_retries had been set to 100, but documented as being + 3, and the interval_max was set to 1 but documented as 0.2. + The default setting are now set to 3 and 0.2 as it was originally + documented. + + Fix contributed by Matt Long. + - Worker: Log messages when connection established and lost have been improved. + - The repr of a crontab schedule value of '0' should be '*' (Issue #972). + - Revoked tasks are now removed from reserved/active state in the worker + (Issue #969) + + Fix contributed by Alexey Zatelepin. + - gevent: Now supports hard time limits using gevent.Timeout. + - Documentation: Links to init scripts now point to the 3.0 branch instead + of the development branch (master). + - Documentation: Fixed typo in signals user guide (Issue #986). + + instance.app.queues -> instance.app.amqp.queues. + - Eventlet/gevent: The worker did not properly set the custom app + for new greenlets. + - Eventlet/gevent: Fixed a bug where the worker could not recover + from connection loss (Issue #959). + + Also, because of a suspected bug in gevent the + BROKER_CONNECTION_TIMEOUT setting has been disabled + when using gevent + + +------------------------------------------------------------------- Old: ---- celery-3.0.9.tar.bz2 New: ---- celery-3.0.11.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-celery.spec ++++++ --- /var/tmp/diff_new_pack.PE8E4C/_old 2012-10-07 19:55:17.000000000 +0200 +++ /var/tmp/diff_new_pack.PE8E4C/_new 2012-10-07 19:55:17.000000000 +0200 @@ -17,7 +17,7 @@ Name: python-celery -Version: 3.0.9 +Version: 3.0.11 Release: 0 Url: http://celeryproject.org Summary: Distributed Task Queue @@ -33,7 +33,7 @@ BuildRequires: python-distribute BuildRequires: python-eventlet BuildRequires: python-gevent -BuildRequires: python-kombu >= 2.4.5 +BuildRequires: python-kombu >= 2.4.7 BuildRequires: python-mock BuildRequires: python-nose-cover3 BuildRequires: python-pyOpenSSL ++++++ celery-3.0.9.tar.bz2 -> celery-3.0.11.tar.bz2 ++++++ ++++ 4511 lines of diff (skipped) -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
