Status of python sdk

[AndriyMulyar]

Hi,

Thanks for starting this project. What remains to be implemented and tested to make this sdk stable?

Thanks!

[janezpodhostnik]

Hi AndriyMulyar. Thank you for your interest.

I'm trying to release an MVP version soon.

Which for me would mean that all the functionality to interact with the FLOW blockchain is there:

• being able to decode/encode json cadence values
• sending scripts and getting results
• sending/signing arbitrary transactions
• getting events/transaction/blocks/accounts from the FLOW grpc
• having CI that runs tests and examples on PRs
• having a lot of tests and good usage documentation

All of the above except the last point is actually covered already. I'm hoping to get that last point covered in the following weeks.

There are certainly still bugs and instabilities, but at the moment there are no known bugs or instabilities 😅. There is a CI pipeline in place to run all the tests (there aren't that many right now) and all of the examples on the most recent emulator version on every release (an on PRs). Which means there is little chance of something really breaking getting released.

I have been using the flow-py-sdk for my own projects and I'm also trying to create a public showcase project, so I know for a fact it can be used.

I would appreciate any feedback from anyone using or wanting to use this SDK. Feedback would make development much faster 😄.

[AndriyMulyar]

Awesome, thank you for the detailed response.

…

On Thu, May 27, 2021, 9:18 AM Janez Podhostnik ***@***.***> wrote: Hi AndriyMulyar. Thank you for your interest. I'm trying to release an MVP version soon. Which for me would mean that all the functionality to interact with the FLOW blockchain is there: - being able to decode/encode json cadence values - sending scripts and getting results - sending/signing arbitrary transactions - getting events/transaction/blocks/accounts from the FLOW grpc - having CI that runs tests and examples on PRs - having a lot of tests and good usage documentation All of the above except the last point is actually covered already. I'm hoping to get that last point covered in the following weeks. There are certainly still bugs and instabilities, but at the moment there are no *known* bugs or instabilities 😅. There is a CI pipeline in place to run all the tests (there aren't that many right now) and all of the examples on the most recent emulator version on every release (an on PRs). Which means there is little chance of something really breaking getting released. I have been using the flow-py-sdk for my own projects and I'm also trying to create a public showcase project, so I know for a fact it *can* be used. I would appreciate any feedback from anyone using or wanting to use this SDK. Feedback would make development much faster 😄. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJ4TBTCP75WGDS4IQLWCGLTPZBDTANCNFSM45TQAIDQ> .