I suspect this is because graspologic is being installed with development dependencies in most (all?) places in our workflow, and typing_extensions was probably being installed as a dependency of a development dependency. I think this is why I also did not notice as I almost always install locally in dev mode.
We should
check if the above is the case and if so,
add a simple step to the workflow that simply installs graspologic in non-dev mode.
If I'm wrong about the above, then I'd still like to figure out how that snuck past us
Somehow https://github.com/microsoft/graspologic/issues/983 was not caught by our CI/CD workflow
I suspect this is because graspologic is being installed with development dependencies in most (all?) places in our workflow, and
typing_extensions
was probably being installed as a dependency of a development dependency. I think this is why I also did not notice as I almost always install locally in dev mode.We should
If I'm wrong about the above, then I'd still like to figure out how that snuck past us