[rspeer]

Well, shipping an official v2 interpreter with v3 would also necessitate continuing to support the v2 code, including all its quirks that C extension modules use. So what just happened would be a necessary first step.

Then, without the fancy v2-to-v3 bridge, it wouldn't really be more useful than just having both interpreters installed separately.

The fancy bridge does sound like a cool idea. We can run Python 2 or 3 code from Julia (with limitations on the data passed between them), so why can't we run Python 2 code from Python 3, with the same limitations?

It's basically possible already with some RPC libraries, but the experience could certainly be streamlined.