> No-GIL mode is optional Long term the plan is to 100% remove the GIL from python. From the article: > Long-term, we want no-GIL to be the default, and to r

> No-GIL mode is optional Long term the plan is to 100% remove the GIL from python. From the article: > Long-term, we want no-GIL to be the default, and to remove any vestiges of the GIL (without unnecessarily breaking backward compatibility). We don’t want to wait too long with this, because having two common build modes may be a heavy burden on the community (as, for example, it can double test resources and debugging scenarios), but we can’t rush it either. We think it may take as much as five years to get to this stage. Under base assumptions it also says: > We want to be very careful with backward compatibility. We do not want another Python 3 situation, so any changes in third-party code needed to accommodate no-GIL builds should just work in with-GIL builds (although backward compatibility with older Python versions will still need to be addressed).