If it's really not doing any upper bound checks, I could see it blowing up under more mundane conditions; Python includes breaking changes on .x releases, so I've had eg. packages require (say) Python 3.10 when 3.11/12 was current.

I always bring popcorn on major version changes for any programming language. I hope Rust's never 2.0 stance holds.

It would be popcorn-worthy regardless, given the rhetoric surrounding the idea in the community.