-
Notifications
You must be signed in to change notification settings - Fork 6k
Add dispatcher argument to Updater #1484
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
|
Can you fix the open problems marked by CI? |
|
Fixed Flake8 and Codacy (by adding a property to |
|
pre-commit still gives a flake8 error |
Eldinnie
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.
One small change requested
|
I'm also confused to why codecov isn;t running on this. |
|
We can ignore the codecov problem here. Ready to merge |
This allows to pass a pre-initialized
Dispatcherinstance toUpdater, closing #1407.If the new
dispatcherargument is used, attributes likebotandjob_queueare fetched from thedispatcherrather than initializing them.In the docstring tried to make clear that proper initialization of the
dispatcheris up to the user, i.e. it is not checked ifdispatcher.job_queue is not None.Also added tests for creation with
dispatcher. I hope those are enough …