Python’s GIL, a 'major obstacle to concurrency,' will likely be removed – but slowly • DEVCLASS

United States News News

Python’s GIL, a 'major obstacle to concurrency,' will likely be removed – but slowly • DEVCLASS
United States Latest News,United States Headlines
  • 📰 TheRegister
  • ⏱ Reading Time:
  • 65 sec. here
  • 3 min. at publisher
  • 📊 Quality Score:
  • News: 29%
  • Publisher: 61%

Python officials intend to remove the Global Interpreter Lock (GIL) from the language, speeding up concurrent code – and said they will be careful with backward compatibility to avoid “another Python 3 situation.” More here by timanderson over d3vclass

that it intends to accept the proposal, following a poll of the core development team with two questions: were members in favor of making Python free-threaded, and were they willing to accept the cost “in terms of complexity and maintenance.” The votes were 87% in support of the first, and 63% in support of the second, despite the comment in the poll that “We don’t know how much code implicitly relies on the GIL, or is thread-unsafe in subtle ways that are masked by the GIL.

The Steering Council though is wary of the implications and keen to avoid a repeat of the painful progression from Python 2 to Python 3, where lack of compatibility delayed the upgrade for many users. “This is not Python 4,” said the post from core developer Thomas Wouters, posting for the whole Steering Council.

The intent is to progress the proposal in three stages. The first is to add no-GIL as an experimental build, to enable the community to try it. Next, the no-GIL build would become supported, but not the default, for a period of “at least a year or two, possibly more.” Third, the teams wants no-GIL to be the default and “to remove any vestiges of the GIL”.

Gross has been promoting the notion of a no-GIL CPython for some time, and spoke on the subject at the EuroPython event in July 2022, where he said he had been working on the project for the “past few years.” The GIL, he, “ensures that only one thread can execute Python code at a time.” It was introduced in 1992 to enable multi-threaded coding in Python subject to the constraints of the GIL, which made such code safer and easier to implement.

The rationale is compelling; but the compatibility issues are also real, and it seems that the Steering Council is keenly aware of both aspects.

We have summarized this news so that you can read it quickly. If you are interested in the news, you can read the full text here. Read more:

TheRegister /  🏆 67. in UK

United States Latest News, United States Headlines

Similar News:You can also read news stories similar to this one that we have collected from other news sources.

Socket moves beyond JavaScript and Python and gets into GoSocket moves beyond JavaScript and Python and gets into GoCEO, fresh with funds, lays out the dependency dilemma
Read more »

The World Around and Fondation Cartier join forces on series of global eventsThe World Around and Fondation Cartier join forces on series of global eventsThe World Around and Fondation Cartier have announced their collaboration on a series of three public programs in three different cities
Read more »

Global Powers Are Vying For Influence In Eurasia | OilPrice.comGlobal Powers Are Vying For Influence In Eurasia | OilPrice.comCentral Asia and the South Caucasus are intensifying ties, improving cargo transportation, and exploring shared geopolitical interests to better connect Eurasia's two major economies: the EU and China.
Read more »

How U.S. Crude Has Helped Stabilize Global Oil Markets | OilPrice.comHow U.S. Crude Has Helped Stabilize Global Oil Markets | OilPrice.comThe inclusion of WTI Midland crude has made the Brent benchmark more liquid. The more liquid Brent contract has now become less vulnerable to sudden price moves. The EIA has forecast total U.S. output will hit 12.61M bbl/day in the current year.
Read more »



Render Time: 2025-03-04 21:21:46