Jim Crist-Harif

*Note: apologies for the long response* Hmmm, I don't love that (for the description bit). While it's important that whatever syntax is chosen is mypy/pyright compatible, I find it more...

Sorry, to clarify - I'm only talking about different ways to represent the non-functional metadata (title, description, ...). I agree that there are use cases for adding constraints to complex/nested...

Thanks for opening this issue. It's unfortunate that the base type of `IPv4Address` and `IPv6Address` isn't technically public. It's mentioned in the original [ipaddress PEP](https://peps.python.org/pep-3144/), and other validation libraries like...

> I think I have personally been hitting my head against some reasonably sophisticated typing problems that I would not have a problem with using types.Union Can you provide some...

Are there other custom types/combinations of custom types that you're likely to want to use beyond just `IPv4Address`/`IPv6Address`/`IPv4Address | IPv6Address`? I have a plan that would make `IPv4Address | IPv6Address`...

It looks like there's been some work done on this since the last comment, but I can't quite figure out how to make this work myself (if it's even possible)....

> The reason is that I install this package as system-admin, but I run it as my regular user. > Is there anyway to prohibit any file creations like that...

See discussion in #190.

I'm not saying doing reductions with float16 makes sense, I'm just saying that I don't think what we're doing 100% matches semantically what numpy is doing. By semantically, I mean...

> msgspec looks promising https://github.com/jcrist/msgspec which can save memory when using a predictable schema. `msgspec` has a pretty efficient parser, and should have lower memory usage than other options like...