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 neologix
Recipients Albert.Zeyer, neologix, pitrou, r.david.murray
Date 2013-02-23.10:55:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3jroBv5Cm5dD=OgSrsGJtKzZa=2QCvCqwH0kTEcEummw@mail.gmail.com>
In-reply-to <1361615903.66.0.607703989117.issue17263@psf.upfronthosting.co.za>
Content
> This shouldn't be a problem in Python 3 where Python threads cannot switch
> during shutdown.

What happens if the GIL is relased during shutdown?

Also, I'm a bit worried about this code:
"""
void
PyThreadState_Clear(PyThreadState *tstate)
{
    if (Py_VerboseFlag && tstate->frame != NULL)
        fprintf(stderr,
          "PyThreadState_Clear: warning: thread still has a frame\n");

    Py_CLEAR(tstate->frame);

    Py_CLEAR(tstate->dict);
"""

The TLS dict is deallocated after having cleared the frame, which
could lead to surprises, no?
History
Date User Action Args
2013-02-23 10:55:38neologixsetrecipients: + neologix, pitrou, r.david.murray, Albert.Zeyer
2013-02-23 10:55:38neologixlinkissue17263 messages
2013-02-23 10:55:38neologixcreate