-
-
Notifications
You must be signed in to change notification settings - Fork 96
Warn if result backend is unset #430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@s3rius Maybe we should add a warning for other task methods if the result backend is not set. What do you think? |
s3rius
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion the isinstance method is quite expensive to call. We can just add raise in the DummyBackend itself.
Because this isinstance call will be triggered for any ResultBackend. Which might decrease performance.
|
I'm wondering. Maybe it'd be better to use warn module to make warnings appear even if you haven't configured logging. |
* warn on .wait_result call if there is no result backend * warn user on dummy result backend level * use warn from warnings module --------- Co-authored-by: Pavel Kirilin <[email protected]>
* warn on .wait_result call if there is no result backend * warn user on dummy result backend level * use warn from warnings module --------- Co-authored-by: Pavel Kirilin <[email protected]>
#427