Jeremy Maitin-Shepard

I believe I've now addressed all of the review comments and outstanding issues. Type parameters are still not handled, but that is largely orthogonal to PEP 695 type alias support.

There is still one issue remaining with how type alias objects are stringified in stringify_annotation that I need to look into.

> There is still one issue remaining with how type alias objects are stringified in stringify_annotation that I need to look into. I think it is okay as is actually....

@AA-Turner I think this is ready now.

I had intended that explicitly created `typing_extensions.TypeAliasType` objects would still be supported even on Python < 3.12. As far as using `autoclass` vs a separate directive: The main reason to...

@AA-Turner thanks!

It appears that at least some tensorstore symbols have somehow ended up with global visibility across the two extension modules. Symbol visibility for Python extension modules is tricky. Normally you...

The issue is that tensorstore uses multiple threads internally and therefore isn't fork-safe. It will probably work if you can arrange not to use tensorstore before forking.

Are you referring to the NumPy fixed-length (zero-padded) string data types, like "|S10" or "

We decided to remove them, at least initially, because they introduced a lot of complications and the value was unclear. - "O" (python object): This is essentially meaningless as a...