-
Notifications
You must be signed in to change notification settings - Fork 7
[WIP] Make serializer interface streaming #20
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: master
Are you sure you want to change the base?
Conversation
Also updates some ~= matches as I had used them incorrectly: * `~= 2.7` = `>= 2.7, == 2.*` * `>= 2.7.0` = `>= 2.7.0, == 2.7.*` !
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.
@Alexander255 Can you please code some tests also?
…ods in adapters Previously `.contains()` would always be forwarded, while `.get_all()` would *usually* be emulated using `(await .get()).collect()`. Now both are emulated by default (simplifies writing new adapters) with the option to set some constants on the class to forward them instead.
Previously it was in the command-line switches in `tox.ini` and `mypy_run.py`.
@AliabbasMerchant: But it does have tests? (Only commit acd5245 is relevant, the rest is an old version of #19.) |
@Alexander255 I overlooked the tests file 🤦♂ |
After some consideration I decided to revise the proposed serializer interface to decouple the serializers from the I/O framework and use a |
Fixes #4, depends on #19.
Uses the JSON decoder from
py-ipfs-api-client
, but may switch toijson
in the future. Thepickle
implementation still reads the entire stream before beginning parsing, but it's more a proof-of concept anyways.