aboutsummaryrefslogtreecommitdiff
path: root/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
diff options
context:
space:
mode:
Diffstat (limited to 'source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md')
-rw-r--r--source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md b/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
index c289dece..6e0ca9b0 100644
--- a/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
+++ b/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
@@ -1,7 +1,7 @@
---
title: "Graceful handling of <code>SIGINT</code> when using Python's <code>multiprocessing.Process</code>"
date: 2015-05-05T22:03:39-07:00
-date-display: May 5, 2015
+date_display: May 5, 2015
---
Today I learned something about Python's (at least CPython's) multiprocessing and signal handling, and I would like to share it here. Basically my situation was such (when developing [`pydoc`](https://github.com/zmwangx/zmwangx.github.io/blob/source/pyblog) that powers this blog):