Exception in schedule callback -> Assertion failed,https://bitbucket.org/stackless-dev/stackless/issues/new taskletobject.c, line 51 about stackless HOT 6 CLOSED

Original comment by Kristján Valur Jónsson (Bitbucket: krisvale, GitHub: kristjanvalur):

This has been fixed in commits 8e5a906 and efefbe0

from stackless.

Original comment by Anonymous:

Yes, if it should make sense to extend this, then it is welcome as an enhancement
proposal, but it is fine to let it be as it is, with exceptions as a warning.
When this feature was requested, back in 2002, it was clearly defined as a notification
only. (I think it was either Matti or Eggert Jón Magnússon)

Hoffe Du hattest auch ein schönes Heiligabend

from stackless.

Original comment by Kristján Valur Jónsson (Bitbucket: krisvale, GitHub: kristjanvalur):

Great, I agree and will make it so.

Frohe Weihnachten!

from stackless.

Original comment by Anonymous:

This was never supposed to happen. The callback is meant for monitoring.
I guess any exception should be ignored, maybe issuing a warning.
That is at least consistent.

Merry Xmas, btw. ;-)

from stackless.

Original comment by Kristján Valur Jónsson (Bitbucket: krisvale, GitHub: kristjanvalur):

The problem is that an exception is being raised when the tasklet has ended. The exception is trying to abort the switch, but there is no way to abort the ending of the tasklet. What is supposed to happen? Are these callbacks supposed to be able to abort switching?

from stackless.

Original comment by Anselm Kruis (Bitbucket: akruis, GitHub: akruis):

Commit id is 5c76a6fd228f

from stackless.