Added Workflows #72
Open
Added Workflows #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If we specify a custom event loop at worker instantiation, it has to also be used by asyncio instead of default one.
Pass loop attribute to asyncio.ensure_future
Rename package and fix configuration files
Will be be re-enabled later
Prepare first release
Change title to show it's a fork
…ming Add crontab timer function to run periodic job
run black and isort on all python files
Note that this doesn’t change the parameters of functions. They still accept loop arguments, even if they are unused. Changing the API to account for unused variables will come in a later commit.
test on python 3.10
let pypi know mode supports 3.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: Before submitting this pull request, please review our contributing
guidelines.
Description
added workflows b/c this hasn't been updated in a while.
NOTE: All patches should be made against master, not a maintenance branch like
3.1, 2.5, etc. That is unless the bug is already fixed in master, but not in
that version series.
If it fixes a bug or resolves a feature request,
be sure to link to that issue via (Fixes #4412) for example.