|
4 | 4 | Changes in Jupyter Client
|
5 | 5 | =========================
|
6 | 6 |
|
| 7 | +5.2 |
| 8 | +=== |
| 9 | + |
| 10 | +`5.2 on GitHub <https://github.com/jupyter/jupyter_client/milestones/5.2>`__ |
| 11 | + |
| 12 | +- Define Jupyter protocol version 5.3: |
| 13 | + |
| 14 | + - Kernels can now opt to be interrupted by a message sent on the control channel |
| 15 | + instead of a system signal. See :ref:`kernelspecs` and :ref:`msging_interrupt` |
| 16 | + (:ghpull:`294`). |
| 17 | + |
| 18 | +- New ``jupyter kernel`` command to launch an installed kernel by name |
| 19 | + (:ghpull:`240`). |
| 20 | +- Kernelspecs where the command starts with e.g. ``python3`` or |
| 21 | + ``python3.6``—matching the version ``jupyter_client`` is running on—are now |
| 22 | + launched with the same Python executable as the launching process (:ghpull:`306`). |
| 23 | + This extends the special handling of ``python`` added in 5.0. |
| 24 | +- Command line arguments specified by a kernelspec can now include |
| 25 | + ``{resource_dir}``, which will be substituted with the kernelspec resource |
| 26 | + directory path when the kernel is launched (:ghpull:`289`). |
| 27 | +- Kernelspecs now have an optional ``metadata`` field to hold arbitrary metadata |
| 28 | + about kernels—see :ref:`kernelspecs` (:ghpull:`274`). |
| 29 | +- Make the ``KernelRestarter`` class used by a ``KernelManager`` configurable |
| 30 | + (:ghpull:`290`). |
| 31 | +- When killing a kernel on Unix, kill its process group (:ghpull:`314`). |
| 32 | +- If a kernel dies soon after starting, reassign random ports before restarting |
| 33 | + it, in case one of the previously chosen ports has been bound by another |
| 34 | + process (:ghpull:`279`). |
| 35 | +- Avoid unnecessary filesystem operations when finding a kernelspec with |
| 36 | + :meth:`.KernelSpecManager.get_kernel_spec` (:ghpull:`311`). |
| 37 | +- :meth:`.KernelSpecManager.get_all_specs` will no longer raise an exception on |
| 38 | + encountering an invalid ``kernel.json`` file. It will raise a warning and |
| 39 | + continue (:ghpull:`310`). |
| 40 | +- Check for non-contiguous buffers before trying to send them through ZMQ |
| 41 | + (:ghpull:`258`). |
| 42 | +- Compatibility with upcoming Tornado version 5.0 (:ghpull:`304`). |
| 43 | +- Simplify setup code by always using setuptools (:ghpull:`284`). |
| 44 | +- Soften warnings when setting the sticky bit on runtime files fails |
| 45 | + (:ghpull:`286`). |
| 46 | +- Various corrections and improvements to documentation. |
| 47 | + |
| 48 | + |
7 | 49 | 5.1
|
8 | 50 | ===
|
9 | 51 |
|
|
0 commit comments