Ticket #63 (new task)

Opened 7 years ago

Last modified 5 years ago

replace signal handler with event handler

Reported by: mmckerns Owned by: mmckerns
Priority: major Milestone: mystic-0.5a
Component: mystic.solvers Keywords:
Cc:

Description

As stated in ticket #62, signal.signal can only be run from the main thread. Catching signals, as done in the mystic-0.1a1 release, is not suited for distributed or parallel computing... or with a GUI front-end. An event handler that understands TCPIP connections needs to replace the use of the python "signal" module.

Change History

comment:1 Changed 7 years ago by mmckerns

This ticket replaces tickets #9 and #62.

Requirements (carried over from ticket #9):

  • must be able to accept programmatic commands (i.e. from a script)
  • must be able to use a programmatic trigger (i.e. is "CTRL-C" ok?)
  • must be able to trap extension code from python (or worse, interact with a job that launched with os.system)

comment:2 Changed 7 years ago by mmckerns

  • Milestone changed from mystic-dev to mystic-0.1a3

comment:3 Changed 6 years ago by mmckerns

  • Milestone changed from mystic-0.2a1 to mystic-0.2a3

comment:4 Changed 5 years ago by mmckerns

  • Milestone changed from mystic-0.3a1 to mystic-0.3a2
Note: See TracTickets for help on using tickets.