cannoli
pydantic-core
| cannoli | pydantic-core | |
|---|---|---|
| 1 | 18 | |
| 771 | 1,270 | |
| - | 1.2% | |
| 10.0 | 9.6 | |
| over 5 years ago | 9 days ago | |
| Rust | Python | |
| MIT License | MIT License |
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.
cannoli
-
Modern Python Performance Considerations
This is a great read, and it's fantastic to see all the work being done to evaluate and improve the language!
Shameless plug alert: the dynamic-nature of the language is actually something that I had studied a few years back [1]. Particularly the variable and object attribute look ups! My work was just a master's thesis, so we didn't go too deep into more tricky dynamic aspects of the language (e.g. eval, which we restricted entirely). But we did see performance improvements by restricting the language in certain ways that aid in static analysis, which allowed for more performant runtime code. But for those interested, the abstract of my thesis [2] gives more insight into what we were evaluating.
Our results showed that restricting dynamic code (code that is constructed at run time from other source code) and dynamic objects (mutation of the structure of classes and objects at run time) significantly improved the performance of our benchmarks.
[1]: https://github.com/joncatanio/cannoli
[2]: https://digitalcommons.calpoly.edu/theses/1886/
pydantic-core
-
Is there a pydantic.BaseSettings equivalent in rust?
Funny that you ask... https://github.com/pydantic/pydantic-core Unfortunately it seems that the functionality you ask for is not (yet) part of this ...
-
Investigating Pydantic v2's Bold Performance Claims
I encourage you to checkout the official benchmarks for more realistic and detailed examples, and, as always, YMMV.
-
Pydantic V2 leverages Rust's Superpowers [video]
> to also be constrained by a separate set of data types which are legal in rust.
This isn't really how writing rust/python iterop works. You tend to have opaque handles you call python methods on. Here's a decent example I found skimming the code.
https://github.com/pydantic/pydantic-core/blob/main/src/inpu...
-
Pydantic vs Protobuf vs Namedtuples vs Dataclasses
Thanks for pointing out to that, I did not know about it. Also attaching repo in case someone would be interested as well - https://github.com/pydantic/pydantic-core
-
Introducing CodSpeed: Continuous Performance Measurement
pydantic-core: The core validation logic for pydantic, a Python data parsing and validation library.
-
Show HN: Python framework is faster than Golang Fiber
pydandic-core [0] will hopefully solve this issue (written in Rust)
[0] -- https://github.com/pydantic/pydantic-core
- Scala or Rust? which one will rule in future?
-
Rust for Data Engineering—what's the hype about? 🦀
LinkedIn influencers are weird lol. Rust v Python is apples and oranges. Rust would be glued together by python just like it does with C/C++ and Java/Spark today. We’re already seeing some packages go this direction, like pydantic v2 is rewriting its core validation in rust.
- Python file structure with Rust extensions
- Pydantic 2 rewritten in Rust was merged