Show HN: Paradict – Streamable multi-format serialization with schema

• paradict

  2 21 5.1 Python

  Streamable multi-format serialization with schema

• braq

  5 7 4.5 Python

  Customizable data format for config files, AI prompts, and more

Under the hood, Paradict uses Braq (https://github.com/pyrustic/braq), the most obvious way to section a document (as shown just above), and Ustrid (https://github.com/pyrustic/ustrid), to uniquely generate string identifiers.

Paradict is available on PyPI and you can learn more by reading its README, browsing the source code or playing with its tests.

Let me know what you think about all this !

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• ustrid

  1 0 3.5 Python

  Uniquely generated string identifiers

Under the hood, Paradict uses Braq (https://github.com/pyrustic/braq), the most obvious way to section a document (as shown just above), and Ustrid (https://github.com/pyrustic/ustrid), to uniquely generate string identifiers.

Paradict is available on PyPI and you can learn more by reading its README, browsing the source code or playing with its tests.

Let me know what you think about all this !

• backstage

  7 16 4.3 Python

  Three-speed scripting language and task automation tool (by pyrustic)

Although most languages allow Unicode characters in identifiers, for better code portability and readability, we agree to stick to ASCII characters. Since we're already sticking to ASCII characters in our source code, I think we'll be less 'astonished' to encounter similar rules for our configuration keys (especially when a key-value pair in the Paradict configuration file looks like an instruction for variable assignment).

> I don't get the a-z benefit in the argument case - the user must type "arg1" precisely for the argument names to match...

Absolutely ! The user must type "arg1" precisely because this is part of the implicit agreement between the user and the system. If the user forgets to type "arg1", the default value will be taken into account. If the user adds an additional unexpected key (a typo for example), it will be stored in "kwargs" and then ignored or used to warn the user.

I plan to build two flagship projects to leverage Paradict binary and textual formats: a lightweight database and an automation tool. The automation tool will consume a configuration file a bit like another project of mine does (https://github.com/pyrustic/backstage).

And this is where I join you. I think we'll both agree that since a shell command is already likely to have quotes around some of its arguments, it's very annoying to put extra quotes around it. So I'm thinking of introducing a Command data type:

  # typing 'start' in the command line will run

Suggest a related project