Kyle Altendorf

I believe we have just implemented different means of passing `None` or `set()`, but that they are the same result? https://github.com/altendky/trio/blob/c079d3cfdf4b91c76cd9aa376d1ddb76db4d40d7/trio/_core/_multierror.py#L405-L423 I tried a GitHub compare but it isn't showing...

I'm confused. It seems like there is overlap between pyserial-supported-things and those that a theoretical libusb based library would support. Am I wrong and a libusb based system would support...

Just passing by because of the `AddressFamily` reference (deciding how to placate pylint) but "paths" aren't always strings and there are tools that I think are for handling the decoding/encoding....

I presume there are functions that always return paths as `str` but "paths" (a fairly general concept, admittedly) are not exclusively `str` nor even `str` based. It seems that `surrogateescape`...

I haven't compared in detail, but I think https://github.com/python-trio/trio/pull/1921 touches on this issue?

Re: https://github.com/python-attrs/attrs/pull/404#issuecomment-462108964 I like the idea of a general hook from which the user can describe conversion/validation/.... But, what here let's me take a class that I've defined which validates...

I don't remember the details to make it more concrete than in the OP, sorry. That said, being able to construct a class instance without explicitly writing out the parameters...

This came up again in `#python`. Present interest is to be able to have `x: int` act as `x: int = attr.ib(converter=int)`. Having the `__init__` name would allow this to...

Thanks. I clearly need to read up on field transformers and learn this 'new' feature.

@gvoysey AFAIK valid attribute, uh, things, and attribute names you can type in code are not the same set. You can `getattr(the_object, 'some string-with . all sorts? of weird stuff')`...