pkgsrc/devel/py-jupyter_client/Makefile

37 lines
1.2 KiB
Makefile
Raw Normal View History

# $NetBSD: Makefile,v 1.8 2018/04/05 12:38:57 adam Exp $
DISTNAME= jupyter_client-5.2.3
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
CATEGORIES= devel python
MASTER_SITES= ${MASTER_SITE_PYPI:=j/jupyter_client/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://jupyter.org/
COMMENT= Jupyter protocol implementation and client libraries
LICENSE= modified-bsd
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.
2017-12-30 12:30:13 +01:00
DEPENDS+= ${PYPKGPREFIX}-dateutil>=2.1:../../time/py-dateutil
DEPENDS+= ${PYPKGPREFIX}-jupyter_core-[0-9]*:../../devel/py-jupyter_core
DEPENDS+= ${PYPKGPREFIX}-tornado>=4.1:../../www/py-tornado
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.
2017-12-30 12:30:13 +01:00
DEPENDS+= ${PYPKGPREFIX}-traitlets>=4.1.0:../../devel/py-traitlets
DEPENDS+= ${PYPKGPREFIX}-zmq>=13.0.0:../../net/py-zmq
TEST_DEPENDS+= ${PYPKGPREFIX}-ipykernel-[0-9]*:../../devel/py-ipykernel
TEST_DEPENDS+= ${PYPKGPREFIX}-test-[0-9]*:../../devel/py-test
PYTHON_VERSIONED_DEPENDENCIES= ipython:test
USE_LANGUAGES= # none
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.
2017-12-30 12:30:13 +01:00
post-install:
cd ${DESTDIR}${PREFIX}/bin && \
${MV} jupyter-kernel jupyter-kernel${PYVERSSUFFIX} && \
${MV} jupyter-kernelspec jupyter-kernelspec${PYVERSSUFFIX} && \
${MV} jupyter-run jupyter-run${PYVERSSUFFIX} || ${TRUE}
do-test:
cd ${WRKSRC} && py.test-${PYVERSSUFFIX}
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.
2017-12-30 12:30:13 +01:00
.include "../../lang/python/egg.mk"
.include "../../lang/python/versioned_dependencies.mk"
.include "../../mk/bsd.pkg.mk"