Welcome Team! #1
Replies: 4 comments 6 replies
-
|
my suggestion for scope let's keep it pure serialization. my understanding is toon is not a data processing library?
same approach as json and yaml |
Beta Was this translation helpful? Give feedback.
-
|
Hi team! 👋 ✅ uv for package management Regarding PyPI: Both toon-python and toon-format are already taken. However, I currently own python-toon on PyPI. If the team agrees, we could use pip install python-toon as the official package and I can transfer ownership to the toon-format organization when we're ready.
Scope Agreement encode(dict) → str and decode(str) → dict This keeps it simple, follows the json/yaml philosophy, and avoids scope creep. |
Beta Was this translation helpful? Give feedback.
-
|
PS: I haven't added your names to either the README and License. Please add them in one of the following PRs. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I just found this. I want to propose my idea to use Rust as a backend to enhance encode/decode speed. I've done some work in my repo here. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @bpradana, @davidpirogov, @xaviviro, and @Justar96! 👋
Following our discussion in #54, the official Python implementation repo is now ready. All of you have been invited as maintainers.
What's Ready
This Repository
You now have full access to toon-format/toon-python. This is where you can build the consolidated Python implementation together.
Language-Agnostic Tests
I have finished the language-agnostic: The spec repository now includes language-agnostic test fixtures that all implementations can use:
tests/fixtures/encode/)tests/fixtures/decode/)These JSON fixtures ensure consistency across all language implementations and make it easy to validate spec compliance.
Next Steps
Based on your feedback, Option A (pick the strongest foundation) was the consensus. Here's how to move forward:
Note
You can touch every file in this repo – I've only set up a base without much knowledge about Python. Feel free to challenge everything!
Initial Setup:
Collaborate:
Key Priorities
From the discussion, here's what we're aligned on:
Future milestones discussed:
Team Work
Please be kind to each other. I've something is off or you experience troubles in the team, please DM me and we get this sorted out.
Let's Get Started
Feel free to open issues to kick off discussions about:
Thank you all for stepping up to collaborate on this. Looking forward to what you're going to build! 🎉
P.S. – Release tokens for PyPI publishing will be added to the repo's environment secrets once we're ready to publish.
Beta Was this translation helpful? Give feedback.
All reactions