Looks like a legitimate issue to me, and the patch is fine. It's probably something that ought to be fixed in default too, since I don't see how it is restricted to session 0 - any Python service will incorrectly treat these notifications as interruptions.

Sent from my Windows Phone
________________________________
From: Zachary Ware<mailto:report@bugs.python.org>
Sent: ‎7/‎8/‎2014 15:45
To: Steve Dower<mailto:Steve.Dower@microsoft.com>
Subject: [issue20513] Python 2.7. Script interruption on logoff from 0 session under Win2003 and earlier

Zachary Ware added the comment:

Windows Server 2003, XP, and 2000 are all officially supported by Python 2.7, as they were all current (for certain values of "current") at the time Python 2.7 was released.

That said, it's not completely clear to me what the bug is but it strikes me as being something that's not all that likely to be hit, and either way about it, I don't have any way to test it.

----------

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue20513>
_______________________________________