valdec
Decorator for validating function arguments and result (by EvgeniyBurdin)
koda-validate
Typesafe, Composable Validation (by keithasaurus)
valdec | koda-validate | |
---|---|---|
1 | 10 | |
13 | 108 | |
- | - | |
2.7 | 5.2 | |
over 3 years ago | 27 days ago | |
Python | Python | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
valdec
Posts with mentions or reviews of valdec.
We have used some of these posts to build our list of alternatives
and similar projects.
-
What is the correct way to validate user input?
One way to do it would be to have validation decorators wrap your function. The general idea is expanded upon in this module
koda-validate
Posts with mentions or reviews of koda-validate.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-23.
-
Pydantic V2 leverages Rust's Superpowers [video]
As someone who built a pure python validation library[0] that's much faster than pydantic (~1.5x - 12x depending on the benchmark), I have to say that this whole focus on Rust seems premature. There's clearly a lot of room for pydantic to optimize its Python implementation.
Beyond that, rust seems like a great fit for tooling (i.e. ruff), but as a library used at runtime, it seems a little odd to make a validation library (which can expect to receive any kind of data valid python data) to also be constrained by a separate set of data types which are valid in rust.
[0]: https://github.com/keithasaurus/koda-validate
-
beartype: It has documentation now. It only took two years, my last hair follicle, precious sanity points (SPs), and working with Sphinx. Don't be like @leycec. Go hard on documentation early.
For the sake of comparison I built a validate_signature function as part of koda-validate, which has a lot of overlap with beartype. I haven't really compared it to beartype, so I'd be interested to see people's thoughts on how the two approaches compare.
-
Pydantic vs Protobuf vs Namedtuples vs Dataclasses
FYI I wrote koda-validate, which is significantly faster than pydantic, has a similar API, and is pure python.
- Koda Validate: Alternative to Pydantic that is faster, more flexible, and async-compatible.
- I built a composable validation library. It plays nice with type hints and asyncio. Would love some feedback!
- Koda Validate: Flexible, Explicit, Async-compatible Validation in Python
- Show HN: Koda Validate 2.0 – Async Validation in Python
-
This Week In Python
koda-validate – Typesafe Validation
- Show HN: Koda Validate – Typesafe, combinable validation for Python