-
-
Notifications
You must be signed in to change notification settings - Fork 440
refactor: use asyncio & AsyncSSH, introduce AsyncContext #1482
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
base: 3.x
Are you sure you want to change the base?
Conversation
…nd introduce AsyncContext helper
…nd deprecation warnings for Paramiko kwargs
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.
Wow! This is incredible work, @JakkuSakura. I think moving to asyncio is definitely the way forward - I actually think we should make pyinfra's API async only and remove the complexity of having the two context types.
I still need to read through the PR in full, but generally this looks amazing, nice that the API changes aren't actually too crazy. I'd like to figure out how we can make the API accessible with minimal boilerplate, I think this is possible if we go all async.
Going to reach out (email) to figure out how we can best land this (and 4.x).
Glad to hear this. I'm going to use this branch in my own project to see if it causes any issues |
Pull request is based on the default branch (3.x
at this time)scripts/dev-test.sh
)scripts/dev-lint.sh
)closes #1478
closes #1474