Releases: ivknv/yadisk-async
Release 1.4.5
Release 1.4.4
— upload()
and download()
(and related) methods can now upload/download non-seekable file-like objects (e.g. stdin
or stdout
when open in binary mode), see PR ivknv/yadisk#31
Release 1.4.3
— app:/
paths now work correctly (see issue ivknv/yadisk#26)
Release 1.4.2
— Fixed ivknv/yadisk#29: TypeError: 'type' object is not subscriptable
— Fixed a bug affecting Python <3.9: TypeError: Too many parameters for typing.AsyncIterable; actual 2, expected 1
Release 1.4.1
— Fixed ivknv/yadisk#28: download_public()
with path keyword argument raises TypeError
— Fixed AttributeError
raised when calling ResourceLinkObject.public_listdir()
Release 1.4.0
— Added convenience methods to :code:...Object
objects (e.g. see :code:ResourceObject
in docs)
— Added type hints
— Improved error checking and response validation
— Added InvalidResponseError
, PayloadTooLargeError
, UploadTrafficLimitExceededError
— Added a few missing fields to DiskInfoObject
and SystemFoldersObject
— Added rename()
, upload_by_link()
and download_by_link()
methods
— Added default_args
field for YaDisk
object
— download()
and :code:upload()
now return ResourceLinkObject
— Returned LinkObject
instances have been replaced by more specific subclasses
— ConnectionError
now also triggers a retry
— Added support for async files for download()
and upload()
— Use aiofiles
to open files by default
Release 1.3.6
— Fixed ivknv/yadisk#26: ':' character in filenames causes BadRequestError
. This is due the behavior of Yandex.Disk's REST API itself but is avoided on the library level with this fix.
Release 1.3.5
— Fixed a bug in is_file()
and is_dir()
: a typo was causing AttributeError
(PR #6).
Release 1.3.4
— Fixed a bug in check_token()
: could throw ForbiddenError
if the application lacks necessary permissions (issue #23).
Release 1.3.3
— Fixed an issue where http://
links were not recognized as operation links (they were assumed to always be https://
, since all the other requests are always HTTPS). Occasionally, Yandex.Disk can for some reason return an http://
link to an asynchronous operation instead of https://
. Both links are now recognized correctly and an https://
version will always be used by get_operation_status()
, regardless of which one Yandex.Disk returned.