Skip to content
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

feat: convert to async #48

Merged
merged 9 commits into from
Nov 13, 2019
Merged

feat: convert to async #48

merged 9 commits into from
Nov 13, 2019

Conversation

alandtse
Copy link
Collaborator

This version contains numerous changes in addition to the async conversion. It includes a new charging sensor, support for oauth, performance tweaks, and incorporation of black for formatting.
BREAKING CHANGE: API calls now require async
Closes #44, #47

This version contains numerous changes in addition to the async conversion. It includes a new charging sensor, support for oauth, performance tweaks, and incorporation of black for formatting.
BREAKING CHANGE: API calls now require async
Closes zabuldon#44, zabuldon#47
@alandtse
Copy link
Collaborator Author

To test this, use this branch of HA. I will be submitting it after a few days testing.

@alandtse alandtse mentioned this pull request Oct 28, 2019
Copy link
Owner

@zabuldon zabuldon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By the way. Do we really want to remove "sync" functions?

requests = "*"
aiohttp = "*"

[pipenv]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's freeze versions.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we rely on the Pipfile.lock file?

pylintrc Outdated Show resolved Hide resolved
setup.cfg Show resolved Hide resolved
@alandtse
Copy link
Collaborator Author

Whenever you're ready to merge this the semantic-release workflow should kick in. It's currently set with a --noop flag so we can confirm it thinks the next release is v1.0.0. We'll need to remove that --noop flag to test the github upload and pypi release. I believe all those credentials should work as the debug is showing they aren't blank (they're masked though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Swap to async
2 participants