[issue16862] FAQ has outdated information about Stackless

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed type: -> enhancement ___ Python tracker

[issue16862] FAQ has outdated information about Stackless

Roundup Robot added the comment: New changeset d2867c430333 by Ezio Melotti in branch '3.2': #16862: remove outdated statements about Stackless. http://hg.python.org/cpython/rev/d2867c430333 New changeset b66049748535 by Ezio Melotti in branch '3.3': #16862: merge with 3.2. http://hg.python.org/

[issue16862] FAQ has outdated information about Stackless

Terry J. Reedy added the comment: I think answer 2 should just say "An alternative is Stackless Python." and let interested people click the link. The entire second sentence should go, and I am not sure how much of the rest of the first is still correct, as Stackless has changed from when it w

[issue16862] FAQ has outdated information about Stackless

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue16862] FAQ has outdated information about Stackless

Ramchandra Apte added the comment: Sorry, link here, http://docs.python.org/3/faq/design.html#can-t-you-emulate-threads-in-the-interpreter-instead-of-relying-on-an-os-specific-thread-implementation . -- ___ Python tracker

[issue16862] FAQ has outdated information about Stackless

New submission from Ramchandra Apte: The FAQ says "It’s [Stackless] still experimental but looks very promising." AFAIK, Stackless is mature. -- assignee: docs@python components: Documentation messages: 179038 nosy: docs@python, ramchandra.apte priority: normal severity: normal status: