🔷 [Epic] Python Contracts SDK Milestone 2

[frol]

Background

We'd like to appeal to Python devs building on NEAR end-to-end. See #1 for Milestone 1

Scope

Context: https://www.reddit.com/r/Python/comments/1huxrs6/python_running_on_wasm_near_under_1mb_challenge/

Milestone 2 is getting a minimal viable implementation that devs can already use to build minimal contracts in Python. Minimal requirements: RustPython/RustPython#5467 (reply in thread)

Related Initiative

No response

Related Tasks

No response

Priority

🟡 P2 : Medium

[frol]

We are on track! https://github.com/orgs/micropython/discussions/16427#discussioncomment-11986599

Missing bits:

• Python exceptions support
• Windows support
• MacOS testing
• Testing suite
• NFT example
• FT example - we have low-level and high-level examples now
• Cleaned up README tailored towards contract developers and not the SDK developers (consider moving the current README to CONTRIBUTING.md) - Ricky took it over with near-sdk-py refactoring
• Move to github.com/near org under near-sdk-py name - let's keep it outside of near org to promote decentralization

[frol]

I have tweeted and messaged in telegram about Python SDK quite a few times already and the devs are excited. I will do a livecoding stream today.

[past-hypothesis]

At first glance, it looks like all of the requirements are met here: https://github.com/past-hypothesis/near-py-tool

NFT example built using the low-level API is here, as a part of the test suite: https://github.com/past-hypothesis/near-py-tool/blob/main/near_py_tool/tests/non_fungible_token.py

Please let me know if anything else needs to be improved

[frol]

@past-hypothesis It looks like it all the items are completed. Let's stop contributing to near-py-tool monolith and as part of Milestone 3 focus on evolving the individual components that @r-near has extracted.

[frol]

Please, create Milestone 2 request on DevHub