Does mojo plan on keeping up Python support?

How fast will mojo release a new version supporting newer python, granted one comes out?
Is there a need to support the newest version as soon as possible?
Does mojo plan on keeping the parity close to Python?
Will mojo deprecate Python runtime support eventually, once the stdlibs are populated?

My understanding is that CPython will eventually become unnecessary.

In terms of mojo, or in general? CPython is there as an Entrypoint, a reliable standard

In terms of Mojo. It’ll eventually be unnecessary for Mojo to use CPython as an interface into the Python ecosystem.

My understanding is that Python runtime support will be deprecated only once Mojo is both source and bug compatible with CPython, meaning that cpython support only goes away once I can put alias python3=mojo run in my .bashrc with no concerns, since at that point cpython support means you are deciding to make your code slower for some reason.

4 Likes

Yes. I’m sure I’ve watched a podcast where Chris said the long-term plan is to be able to run Python dependencies with c extensions without CPython.

I probably should have saved that.

I am a big legacy code supporter. Think backward compatibility in gaming for example. There should always be a backup of the original source code stored somewhere. Even archive them.