Aiogoogle

Latest version: v5.7.0

Safety actively analyzes 630450 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 7

3.1.0

Features

Expose the `raise_for_status` flag in send methods + add an example.
Thanks to Gitznik

3.0.0

Breaking changes

Turned aiogoogle's param validation logic off by default.
This shouldn't affect you unless you were relying on `ValidationError`s to catch input errors.
Now that it's off by default, a 400 error will be thrown with the details of the bad request printed. The details are returned by Google in the JSON body of the response.

For more context on why this feature got turned off by default please read issue 69
If you want to keep using Aiogoogle's internal validation logic, pass `validate=True` to either the API method call e.g. `youtube.videos.list(validate=False)` or to aiogoogle.discover e.g. `aiogoogle.discover('youtube', 'v3', validate=True)`.

2.1.1

Bugs

Fix issue 71 and 72

2.1.0

Features

Add the option to upload bytes object

Thanks to

Andrea Ghensi sanzoghenzo

2.0.1

Bug fixes

- Fixed a bug were multipart headers for content-type were incorrectly configured. Also, now adding JSON to all multipart requests even if it's empty.
- closes 46
- closes 64

2.0.0

Bug fixes

Now quoting path parameters with `urllib.quote` instead of `urllib.quote_plus`

Will my stuff break?

Unless you are passing strings as url path parameters in POST requests (which is unlikely), you should upgrade to v2 without a thought. Otherwise, please read this issue for more details: https://github.com/omarryhan/aiogoogle/issues/63#issuecomment-882027006

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.