Issue 762198: bug in signal.signal -- raises SystemError (original) (raw)

Created on 2003-06-28 00:04 by mccoy, last changed 2022-04-10 16:09 by admin. This issue is now closed.

Messages (9)
msg16641 - (view) Author: Jim McCoy (mccoy) Date: 2003-06-28 00:04
Summary pretty much says it all. Using Py2.2.3, win2k (sp4), and twisted 1.0.5 and the call that is triggering the error is as follows: signal.signal(signal.SIGINT, self.sigInt) returns "SystemError: error return without exception set" The twisted gang has tracked it down to a C error of some sort here...
msg16642 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-06-30 16:06
Logged In: YES user_id=6380 I don't have Win2K, but on Win98 I can't reproduce it. The bug report is pretty incomplete -- the call doesn't seem to need Twisted, so what I tried was this: >>> from signal import * >>> signal(SIGINT, lambda *a: None) This returns the previous handler as it should. So please, send more precise data about the problem, or be ignored.
msg16643 - (view) Author: Phillip Ryals (paryl) Date: 2003-07-01 17:22
Logged In: YES user_id=813621 I can reproduce the problem without importing twisted... Win2k/Python 2.2.2/wxPython 2.4.1.2 >> from signal import * >> signal(SIGINT, lambda *a: None) does not give the error. >> from signal import * >> from wxPython.wx import * >> signal(SIGINT, lambda *a: None) gives the error.
msg16644 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-07-01 17:25
Logged In: YES user_id=6380 OK, there's a clue. Do you know how to report bugs in wxPython?
msg16645 - (view) Author: Phillip Ryals (paryl) Date: 2003-07-02 12:47
Logged In: YES user_id=813621 I already submitted a report on the wxWindows tracker... at the request of a couple of the Twisted guys, I replied to this thread too. I'm dying for a resolution on the matter, so if there's anywhere else I can post this info, please let me know.
msg16646 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-07-02 13:12
Logged In: YES user_id=6380 > I'm dying for a resolution on the matter If you really want this resolved, you're going to have to crawl into a debugger and work it yourself. Open Source means you get to contribute, too. :-)
msg16647 - (view) Author: Phillip Ryals (paryl) Date: 2003-07-03 12:47
Logged In: YES user_id=813621 my, my. I do contribute, in fact. Unfortunately, not knowing the many facets of wxWindows is a small (read: large) problem. Generally you get the people that actually work on a package to fix the package... I find it best to follow the 'non-nuked planet scenario' where getting something done doesn't mean learning it all from scratch because no one else exists with the knowledge. Call me crazy... I mean no offense, of course. ;)
msg16648 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-07-03 13:06
Logged In: YES user_id=6380 > Generally you get the people that actually work on a package > to fix the package... Right. And since they do it in their spare time, you don't get to tell them what their priorities should be.
msg16649 - (view) Author: Robin Dunn (robind) Date: 2003-07-16 23:24
Logged In: YES user_id=53955 This fix for this has just been checked in to wxWindows CVS (use WX_2_4_BRANCH tag)
History
Date User Action Args
2022-04-10 16:09:29 admin set github: 38729
2003-06-28 00:04:03 mccoy create