Tree: d38ac6ca49

0.12-maintenance

1.0-maintenance

master

rtd

0.1

0.10

0.10.1

0.11

0.11.1

0.12

0.12.1

0.12.2

0.12.3

0.12.4

0.2

0.3

0.3.1

0.4

0.5

0.6

0.6.1

0.7

0.7.1

0.7.2

0.8

0.8.1

0.9

1.0

1.0.1

1.0.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'd38ac6ca49'

${ noResults }

Commit Graph

7 Commits (d38ac6ca49e31e670d1bc9a47493fc7a16b3ceb3)

Author	SHA1	Message	Date
Markus Unterwaditzer	b471df6c88	Point to stable version of Celery	10 years ago
Andrew	337a9d6172	Include backend argument when instantiating Celery ... Not including the backend argument can lead to AttributeError: DisabledBackend object has no attribute for '_get_task_meta_for'. See e.g. http://stackoverflow.com/questions/23215311/celery-with-rabbitmq-attributeerror-disabledbackend-object-has-no-attribute. At the same time, including the backend argument doesn't seem to harm anything else.	10 years ago
defuz	02694d609f	docs: :command:`pip`, :option:`--debug`	10 years ago
Alex Pearce	3d6de4dd79	Explicitly pass the Celery instance name. ... When starting a Celery worker module, it is assumed that the Celery instance within the module is called `app`. This is not the case in the Celery pattern, where it is called `celery`, and so must be explicitly referenced.	11 years ago
Afik	67c165bcbb	Update celery.rst ... With the latest version of Celery (3.1.6), following this tutorial produces the following error when attempting to start the celery worker: user_preload = tuple(self.app.user_options['preload'] or ()) AttributeError: 'Flask' object has no attribute 'user_options' Using `app` as the variable name here confuses celery. Renaming `app` to `flask_app` in the tutorial solves the issue and allows the celery worker to start successfully.	11 years ago
Armin Ronacher	05f162329d	Added celery pattern	12 years ago