PyUtilib / pyutilib

64%

master: 62%

LAST BUILD ON BRANCH signal-handling-default

branch: signal-handling-default

CHANGE BRANCH

x

Reset

• signal-handling-default
• 5.3.5
• 5.4
• 5.4.1
• 5.5
• 5.5.1
• 5.6
• 5.6.1
• 5.6.2
• 5.6.3
• 5.6.4
• 5.6.5
• 5.7.0
• 5.7.1
• 5.7.2
• 5.7.3
• 5.8.0
• 6.0.0
• admin-update
• circleci_2
• compatability_updates
• config-display-update
• config-updates
• configblock-doc-gen
• configblock-fixes
• configblock-implicit-duplication
• configblock_call_opts
• excel_fix
• file-comp-fixes
• finalize-release
• finalize-release-5.7.1
• fix-yaml-tests
• fix_component_loader
• fix_config_tests
• fix_deprecated_import
• generic_parallelism
• geraldebberink-master
• import-fixes
• import-test-fix
• import-updates
• import_expand_vars
• indenter-fix
• io-rework
• issue-22
• log-formatting
• master
• nightly_not_expensive
• non_namespace
• patch-release-5.6.5
• py38-fixes
• remove_enum
• reset-for-devel
• revert-101-remove_enum
• revert-104-revert-101-remove_enum
• safe_yaml
• standardize-test-names
• subprocess_th_fix
• timer-start-stop
• unittest-compat
• update-changelog
• yaml-ver-fix

Preserving and restoring original signal handlers in run_command

run_command currently (silently) disposes of any handlers that had been
previously set, and does not remove itself after the subprocess is run.
This changes that behavior so that:
 - original handlers are restored after the subprocess is run
 - if there was a callable handler set before calling run_command, we
   will forward the signal on to that handler after killing the
   subprocess.