HackerTrans
トップ新着トレンドコメント過去質問紹介求人

pomponchik

no profile record

投稿

[untitled]

1 ポイント·投稿者 pomponchik·4 か月前·0 コメント

Pristan: The simplest way to create a plugin infrastructure in Python

github.com
2 ポイント·投稿者 pomponchik·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 pomponchik·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 pomponchik·7 か月前·0 コメント

[untitled]

1 ポイント·投稿者 pomponchik·7 か月前·0 コメント

Metacode: The new standard for machine-readable comments for Python

github.com
22 ポイント·投稿者 pomponchik·7 か月前·7 コメント

Skelet – Minimalist, Thread-Safe Config Library for Python

github.com
1 ポイント·投稿者 pomponchik·8 か月前·1 コメント

コメント

pomponchik
·7 か月前·議論
In the Python ecosystem, there are many tools dealing with source code: linters, test coverage collection systems, and many others. Many of them use special comments, and as a rule, the style of these comments is very similar.

But you know what? There is no single standard for such comments. Seriously.

The internal implementation of reading such comments is also different. Someone uses regular expressions, someone uses even more primitive string processing tools, and someone uses full-fledged parsers, including the Python parser or even written from scratch.

This is exactly the problem that this library solves. It describes a simple and intuitive standard for action comments, and also offers a ready-made parser that creators of other tools can use.
pomponchik
·8 か月前·議論
Skelet is a new config storage/validation library for Python. The goal is to provide a minimal API for collecting settings in one place, while ensuring thread safety, transactionality, and type/value correctness. Configs can be loaded and validated from TOML, YAML, JSON, and environment variables.

Most libraries like pydantic-settings or dynaconf are great for model-based settings, but they aren’t thread-safe out of the box and don’t handle config mutation atomically. Skelet manages assignments under per-field mutexes (so you won’t see half-applied values or race conditions in concurrent apps), and it supports field-level docs, validation, secret fields (hiding any type), and hooks for value changes.

Meant for production scenarios where config safety matters (services, CLI tools, distributed systems), but also handy for scripts that need explicit config handling.