Rooba
/
attrs
mirror of https://github.com/python-attrs/attrs.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo

This commit is contained in:
Hynek Schlawack 2024-03-18 15:34:38 +01:00
parent 2446e640ca
commit a1053048f1
No known key found for this signature in database
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/overview.md
View File

@ -63,12 +63,9 @@ Do with it as you please.
--- ---
*attrs* also isn't a fully-fledged serialization library. *attrs* also is *not* a fully-fledged serialization library.
While it comes with features like converters and validators, it is meant to be a kit for building classes that you would write yourself – but with less boilerplate. While it comes with features like converters and validators, it is meant to be a kit for building classes that you would write yourself – but with less boilerplate.
If you look for powerful-yet-unintrusive serialization and validation for your *attrs* classes, have a look at our sibling project [*cattrs*](https://catt.rs/) or our [third-party extensions](https://github.com/python-attrs/attrs/wiki/Extensions-to-attrs). If you look for powerful-yet-unintrusive serialization and validation for your *attrs* classes, have a look at our sibling project [*cattrs*](https://catt.rs/) or our [third-party extensions](https://github.com/python-attrs/attrs/wiki/Extensions-to-attrs).
This separation of creating classes and serializing them is a conscious design decision. This separation of creating classes and serializing them is a conscious design decision.
We don't think that your business model and your serialization format should be coupled. We don't think that your business model and your serialization format should be coupled.
This separation of creating classes and serializing them is a conscious design decision.
We don't think that your business model and your serialization format should be coupled.