attrs VS reader

Full support for validation and serialisation of attrs classes and msgspec Structs. Where previously only Pydantic models and types where supported, you can now mix and match any of these three libraries. In addition to this, adding support for another modelling library has been greatly simplified with the new plugin architecture

Pydantic is by far not the only library of its kind, with prominent members of the same class being attrs, cattrs or even plain dataclasses for some use cases.

Anything requiring e.g. setattr, getattr, delattr? Without looking far,

https://github.com/python-attrs/attrs/blob/main/src/attr/_ma...

I was looking for an example of using locals() to "fill a data class from kwargs" or something similar to that. The example here doesn't use locals().

That aside, I generally wouldn't use the kwargs approach shown in this example either. I'd use [dataclasses](https://docs.python.org/3/library/dataclasses.html ) or [attrs](https://www.attrs.org/) instead.

hynek: developer of attrs

I continue to be surprised how easy it can be to consume a SOAP API with the right client libraries. Such as https://docs.python-zeep.org/en/master/ for Python. Now that's not to say it will always work, you can design a terrible API with any mechanism, no SOAP or REST client will help you if the other end has desided to succumb to madness and done something like turn their entire API into just "two endpoints" and driven by the payload content you post to the inbound endpoint, and you have to sit there polling the outbound endpoint with the inbound endpoints response ID because to find out what the eventual response is...

But horror story aside, consuming a decent SOAP endpoint with a good client library can be practically magical.

Between attrs (https://www.attrs.org/), cattrs (https://cattrs.readthedocs.io/), and the aforementioned zeep soap client I've got a serialisation pipeline from soap endpoint into an attrs dataclass with type hints and basic type validation down to a snippet so small it fits right here (type hints removed to minimise size).

  from zeep import helpers

attrs has at least two.

I like this pattern so much, I wrote an article about it; if you want to see what it looks like in real life, check this out.

It can also be used to build bookmarking / read later functionality similar to that of Tiny Tiny RSS; extracting content from arbitrary pages would be pretty helpful here.

To find out more, check out the GitHub repo and the docs, or give the tutorial a try.

[1]: https://death.andgravity.com/query-builder-how#more-init

[2]: https://github.com/lemon24/reader/blob/10ccabb9186f531da04db...

Looking now through the Python API docs, I found the Quoting characters for use in search thing, which may come in handy for something I'm doing for my feed reader library (deduplicating articles). Not sure if I'll vendor it or add sqlite-utils as a new dependency, but it's good to know someone already solved this problem (I have a prototype, but I haven't really tested it).

I'm happy to announce version 2.0 of reader, a Python RSS / Atom / JSON feed reader library.

I'm also working on the 2.0 version of my feed reader library. The backwards compatibility break allows me to clean up a bunch of unnecessary code and fix some bad design decisions; I've deleted 250 lines of code until now, and it's very satisfying.

The exact same problems None has when it's not a valid value. None is different from the variable type, that's why you have Optional[VarType], which is an alias for Union[VarType, None]; you can model this in exactly the same way: Union[VarType, MissingType]; here's an example.

reader is a Python feed reader library – it offers all the high-level things you'd want when making a feed reader app/website, except the actual web app.