Christopher Nielsen

> @essandess there are lint warnings about missing dependencies Yep, this needs a rebase

> @reneeotten It looks like there's a dependency bug with `py38-importlib_metadata` somewhere. This is what I see then I try to install `py38-transformers` in trace mode: > > Details >...

> it's actually the interaction with setuptools I think; I've seen this many times before - it checks whether a package is available (which appears to work in trace mode)...

>> Fair enough. But should CI still fail? > Probably not... Let's give CI one more try. If it fails again, I'll download the raw logs and dig into further.

Just downloaded the logs, and the issues are intertwined: * `py38/py39-tensorflow` isn't building for Monterey, perhaps due to the issues with Bazel. * `py310-tensorflow` doesn't exist yet, which is necessary...

> Groan, no. `py*-tensorflow` is effectively obsolete now that we have `py*-tensorflow-macos` and `py*-tensorflow-metal`. I updated the dependency. It looks like `py-tensorflow` was still being pulled in, via `py-tensorflow-data-validation`. Rebased...

> > Groan, no. `py*-tensorflow` is effectively obsolete now that we have `py*-tensorflow-macos` and `py*-tensorflow-metal`. I updated the dependency. > > It looks like `py-tensorflow` was still being pulled in,...

> Well, we're getting closer, as builds succeed for Python 3.10. But dependency installation allegedly fails for 3.8 and 3.9; though my middle-aged eyes aren't seeing a root cause this...

I'll defer to others who are building for PPC, and/or Universal. @evanmiller , @barracuda156 , anyone...?

Rebased against master, and updated commit message to conform to our standards.