David Vo

This will depend on #170 I think.

Unfortunately it looks like pip doesn't understand PEP 600 yet. But the standard exists so that shouldn't really stop us from doing it anyway I guess.

Looks like pip and PyPI speak PEP 600 now. PyPA's tracking issue: https://github.com/pypa/manylinux/issues/542

pip 20.3 is out now with PEP 600 support. We won't be able to use auditwheel on most of our packages, so we'll have to manually (in CI) rename our...

pydantic-core is written in Rust, so we should have it prebuilt to avoid building it in all of our CI jobs, right? Or am I misunderstanding how our cross-builds work?

PEP 621 has been provisionally accepted: https://discuss.python.org/t/pep-621-round-3/5472/109

Looks like setuptools supports PEP 621 natively since v61: https://github.com/pypa/setuptools/blob/main/CHANGES.rst#v6100 (note: setuptools v59.7 requires Python 3.7+)

It's generally a bad idea to have uppercase in module names anyway, so being opinionated here is probably a good idea to avoid cross-platform issues.

I'm happy to take this up (or mentor someone else who wants to), but I'd need to figure out how to connect to the image stream in a round-robin fashion...

They're grouped by the commands dependency. I presume you mean we should group our CV examples (since we don't install OpenCV things on the robot by default)?