Ask Solem 12 years ago
parent
commit
506074a1ba

+ 0 - 2
celery/bin/beat.py

@@ -40,8 +40,6 @@ The :program:`celery beat` command.
 """
 """
 from __future__ import absolute_import
 from __future__ import absolute_import
 
 
-import os
-
 from functools import partial
 from functools import partial
 
 
 from celery.platforms import detached
 from celery.platforms import detached

+ 0 - 1
celery/bin/events.py

@@ -37,7 +37,6 @@ The :program:`celery events` command.
 """
 """
 from __future__ import absolute_import
 from __future__ import absolute_import
 
 
-import os
 import sys
 import sys
 
 
 from functools import partial
 from functools import partial

+ 1 - 0
celery/five.py

@@ -113,6 +113,7 @@ else:
 
 
     BytesIO = WhateverIO = StringIO         # noqa
     BytesIO = WhateverIO = StringIO         # noqa
 
 
+
 def with_metaclass(Type, skip_attrs=set(['__dict__', '__weakref__'])):
 def with_metaclass(Type, skip_attrs=set(['__dict__', '__weakref__'])):
     """Class decorator to set metaclass.
     """Class decorator to set metaclass.
 
 

+ 2 - 2
celery/schedules.py

@@ -71,8 +71,8 @@ class schedule(object):
 
 
         You can override this to decide the interval at runtime,
         You can override this to decide the interval at runtime,
         but keep in mind the value of :setting:`CELERYBEAT_MAX_LOOP_INTERVAL`,
         but keep in mind the value of :setting:`CELERYBEAT_MAX_LOOP_INTERVAL`,
-        which decides the maximum number of seconds the Beat scheduler can sleep
-        between re-checking the periodic task intervals.  So if you
+        which decides the maximum number of seconds the Beat scheduler can
+        sleep between re-checking the periodic task intervals.  So if you
         dynamically change the next run at value, and the max interval is
         dynamically change the next run at value, and the max interval is
         set to 5 minutes, it will take 5 minutes for the change to take
         set to 5 minutes, it will take 5 minutes for the change to take
         effect, so you may consider lowering the value of
         effect, so you may consider lowering the value of

+ 0 - 1
celery/tests/bin/test_multi.py

@@ -98,7 +98,6 @@ class test_multi_args(Case):
             for arg in args:
             for arg in args:
                 self.assertIn(arg, argv)
                 self.assertIn(arg, argv)
 
 
-
         assert_line_in('*P*jerry@*S*',
         assert_line_in('*P*jerry@*S*',
             [
             [
                 'COMMAND', '-n *P*jerry@*S*', '-Q bar',
                 'COMMAND', '-n *P*jerry@*S*', '-Q bar',

+ 0 - 1
celery/tests/security/test_serialization.py

@@ -1,7 +1,6 @@
 from __future__ import absolute_import
 from __future__ import absolute_import
 
 
 from kombu.serialization import registry
 from kombu.serialization import registry
-from kombu.utils.encoding import ensure_bytes
 
 
 from celery.exceptions import SecurityError
 from celery.exceptions import SecurityError
 from celery.security.serialization import SecureSerializer, register_auth
 from celery.security.serialization import SecureSerializer, register_auth

+ 1 - 1
celery/tests/worker/test_worker.py

@@ -519,7 +519,7 @@ class test_Consumer(Case):
                            args=[2, 4, 8], kwargs={})
                            args=[2, 4, 8], kwargs={})
 
 
         l.task_consumer = Mock()
         l.task_consumer = Mock()
-        qos = l.qos = QoS(l.task_consumer.qos, 1)
+        l.qos = QoS(l.task_consumer.qos, 1)
         current_pcount = l.qos.value
         current_pcount = l.qos.value
         l.event_dispatcher = Mock()
         l.event_dispatcher = Mock()
         l.enabled = False
         l.enabled = False

+ 0 - 2
celery/worker/control.py

@@ -8,8 +8,6 @@
 """
 """
 from __future__ import absolute_import
 from __future__ import absolute_import
 
 
-import os
-
 from kombu.utils.encoding import safe_repr
 from kombu.utils.encoding import safe_repr
 
 
 from celery.five import UserDict, items
 from celery.five import UserDict, items