Make library fully async - #361
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Generic High Entropy Secret | 1fd72a9 | tests/fixtures/ring_oauth.json | View secret |
| - | - | Generic High Entropy Secret | 1fd72a9 | tests/fixtures/ring_oauth.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
c5c000c to
792a671
Compare
4796d3a to
847e434
Compare
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
f5f2558 to
e51903f
Compare
356e2e9 to
ba92749
Compare
## [0.9.0](https://github.com/tchellomello/python-ring-doorbell/tree/0.9.0) (2024-08-21) [Full Changelog](0.8.12...0.9.0) **Release highlights:** - Async support for the library - Removed python 3.8 support **Breaking changes:** - Synchronous api calls are now deprecated. For example calling `Ring.update_data()` will emit a deprecation warning to use `await Ring.async_update_data()` which should be run within an event loop via `asyncio.run()`. See `test.py` for an example. - Calling the deprecated sync api methods from inside a running event loop is not supported. This is unlikely to affect many consumers as the norm if running in an event loop is to make synchronous api calls from an executor thread. - Python 3.8 is no longer officially supported and could break in future releases. **Breaking change pull requests:** - Drop python3.8 support and enable python3.13 in the CI [\#398](#398) (@sdb9696) **Implemented enhancements:** - Make library fully async [\#361](#361) (@sdb9696) **Fixed bugs:** - Small change to modify the timestamp [\#378](#378) (@AndrewMohawk) **Project maintenance:** - Update instructions for releasing and migrate changelog [\#407](#407) (@sdb9696) - Add .vscode folder to gitignore [\#397](#397) (@sdb9696) - Update dependencies [\#396](#396) (@sdb9696) - Reduce lock and stale workflow frequency [\#388](#388) (@sdb9696)
Migrate the library to support async api calls running in an asyncio event loop.
Deprecates the synchronous api calls with a warning and runs the async version on a new event loop.