diff --git a/net/py-wsproto/Makefile b/net/py-wsproto/Makefile index 39516c8109ba..1ef8e7e2d040 100644 --- a/net/py-wsproto/Makefile +++ b/net/py-wsproto/Makefile @@ -1,25 +1,26 @@ PORTNAME= wsproto -PORTVERSION= 1.2.0 -PORTREVISION= 1 +DISTVERSION= 1.3.0 CATEGORIES= net python MASTER_SITES= PYPI PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} MAINTAINER= bofh@FreeBSD.org COMMENT= Sans-IO WebSocket protocol implementation -WWW= https://pypi.org/project/wsproto/ +WWW= https://pypi.org/project/wsproto/ \ + https://github.com/python-hyper/wsproto/ LICENSE= MIT -RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}h11>=0.9.0:net/py-h11@${PY_FLAVOR} -TEST_DEPENDS= ${PYTHON_PKGNAMEPREFIX}pytest>0:devel/py-pytest@${PY_FLAVOR} +BUILD_DEPENDS= ${PY_SETUPTOOLS} \ + ${PYTHON_PKGNAMEPREFIX}wheel>=0:devel/py-wheel@${PY_FLAVOR} +RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}h11>=0.16.0:net/py-h11@${PY_FLAVOR} USES= python -USE_PYTHON= autoplist distutils +USE_PYTHON= autoplist pep517 pytest NO_ARCH= yes -do-test: - @cd ${WRKSRC} && ${PYTHON_CMD} -m pytest -v -rs +post-patch: + @${REINPLACE_CMD} '/license-files/d; s|77|63|g' ${WRKSRC}/pyproject.toml .include diff --git a/net/py-wsproto/distinfo b/net/py-wsproto/distinfo index f07a9ce2906a..6bb21ff4ce82 100644 --- a/net/py-wsproto/distinfo +++ b/net/py-wsproto/distinfo @@ -1,3 +1,3 @@ -TIMESTAMP = 1662314696 -SHA256 (wsproto-1.2.0.tar.gz) = ad565f26ecb92588a3e43bc3d96164de84cd9902482b130d0ddbaa9664a85065 -SIZE (wsproto-1.2.0.tar.gz) = 53425 +TIMESTAMP = 1763047513 +SHA256 (wsproto-1.3.0.tar.gz) = 3f220331388cdf229a08bda06f9a377defadfaab7b0d608484fce726830368f9 +SIZE (wsproto-1.3.0.tar.gz) = 49977 diff --git a/net/py-wsproto/pkg-descr b/net/py-wsproto/pkg-descr index 48ea697587f5..5ef45862bdd5 100644 --- a/net/py-wsproto/pkg-descr +++ b/net/py-wsproto/pkg-descr @@ -1,11 +1,9 @@ A pure-Python implementation of a WebSocket protocol stack. It's written from the ground up to be embeddable in whatever program you choose to use, ensuring that you can communicate via WebSockets, as defined in RFC6455, regardless of your programming paradigm. This does not provide a parsing layer, a network layer, or any rules about concurrency. Instead, it's a purely in-memory solution, defined in terms of data actions and WebSocket frames. RFC6455 and Compression Extensions for WebSocket via RFC7692 are fully supported. - -See also: https://github.com/python-hyper/wsproto/