This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients karzes, terry.reedy, tim.peters
Date 2020-10-05.02:01:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601863278.13.0.330230275257.issue41912@roundup.psfhosted.org>
In-reply-to
Content
"Stackless" is a large topic with a convoluted history. Do the web search. In short, no, it will never go in the core - too disruptive to too many things. Parts have lived on in other ways, watered down versions. The PyPy project captured most of what remains, as optional features. CPython's generators captured the easiest part: after a yield, the C stack space the generator consumed is released, while the Python VM stack space lives on in the heap awaiting possible resumption (but, if/when it's resumed, C stack space is required again).
History
Date User Action Args
2020-10-05 02:01:18tim.peterssetrecipients: + tim.peters, terry.reedy, karzes
2020-10-05 02:01:18tim.peterssetmessageid: <1601863278.13.0.330230275257.issue41912@roundup.psfhosted.org>
2020-10-05 02:01:18tim.peterslinkissue41912 messages
2020-10-05 02:01:17tim.peterscreate