The devs intentionally released a version with Rust as an optional but enabled-by-default dependency. I'm not sure how this counts as "jumped the gun" - it's ba

The devs intentionally released a version with Rust as an optional but enabled-by-default dependency. I'm not sure how this counts as "jumped the gun" - it's basically the only safe way to roll out this change. Given the number of people in the thread who are doing automated updates in production pipelines to the latest published version (there's pushback on having to read announcements, pushback on having to read CI output to see deprecation warnings, etc.), it doesn't seem like there's any other way to get people's attention other than enabling it by default and making it easy to disable it. They left two ways to get things working - you can set an environment variable, or you can pin the previous version, because 3.4 has no functional changes from 3.3.2. (The complete set of changes in this version are dropping Python 2, shipping a newer wheel baseline ABI, adding Rust, and adding type hints. No new features and certainly no security fixes relative to 3.3.2.) What is the other option here?