itsdangerous VS attrs

This major release of Flask is accompanied by major releases of Werkzeug, Jinja2, click, and itsdangerous which we'd also welcome and appreciate testing (their pre releases are installed with the Flask pre release).

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.

Of course, a custom class will work, or attrs, or whatever container works for you.