Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

Avoid initialization of Celery when used as a package #7

Merged
merged 1 commit into from
Jan 6, 2016

Conversation

rlucioni
Copy link
Contributor

@rlucioni rlucioni commented Jan 5, 2016

Previously, a cascade of imports caused a Celery app to be initialized whenever a shared task was imported. This is undesired: the application calling the shared task should be allowed to initialize and use its own Celery app. ECOM-2249.

@jimabramson please review.

@rlucioni rlucioni force-pushed the renzo/avoid-accidental-initialization branch from 49ffb03 to df0e567 Compare January 5, 2016 20:37
@jimabramson
Copy link

👍

Previously, a cascade of imports caused a Celery app to be initialized whenever a shared task was imported. This is undesired: the application calling the shared task should be allowed to initialize and use its own Celery app. ECOM-2249.
@rlucioni rlucioni force-pushed the renzo/avoid-accidental-initialization branch from df0e567 to 6e4dd1a Compare January 6, 2016 17:07
rlucioni pushed a commit that referenced this pull request Jan 6, 2016
Avoid initialization of Celery when used as a package
@rlucioni rlucioni merged commit 13560b5 into master Jan 6, 2016
@rlucioni rlucioni deleted the renzo/avoid-accidental-initialization branch January 6, 2016 18:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants