Log Message:
py-jupyter_client: updated to 5.2.0

5.2
- Define Jupyter protocol version 5.3:
  - Kernels can now opt to be interrupted by a message sent on the control channel
    instead of a system signal. See :ref:kernelspecs and :ref:msging_interrupt
- New jupyter kernel command to launch an installed kernel by name
- Kernelspecs where the command starts with e.g. python3 or
  python3.6—matching the version jupyter_client is running on—are now
  launched with the same Python executable as the launching process.
  This extends the special handling of python added in 5.0.
- Command line arguments specified by a kernelspec can now include
  {resource_dir}, which will be substituted with the kernelspec resource
  directory path when the kernel is launched.
- Kernelspecs now have an optional metadata field to hold arbitrary metadata
  about kernels—see :ref:kernelspecs.
- Make the KernelRestarter class used by a KernelManager configurable
- When killing a kernel on Unix, kill its process group.
- If a kernel dies soon after starting, reassign random ports before restarting
  it, in case one of the previously chosen ports has been bound by another
  process.
- Avoid unnecessary filesystem operations when finding a kernelspec with
  :meth:.KernelSpecManager.get_kernel_spec.
- :meth:.KernelSpecManager.get_all_specs will no longer raise an exception on
  encountering an invalid kernel.json file. It will raise a warning and
  continue.
- Check for non-contiguous buffers before trying to send them through ZMQ
- Compatibility with upcoming Tornado version 5.0.
- Simplify setup code by always using setuptools.
- Soften warnings when setting the sticky bit on runtime files fails
- Various corrections and improvements to documentation.