From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-engineio/
Date: Thu, 6 Jul 2023 03:31:06 +0000 (UTC) [thread overview]
Message-ID: <1688614255.ffdd99b0f4d1467a7aa943bbbc45f3aea8748445.mgorny@gentoo> (raw)
commit: ffdd99b0f4d1467a7aa943bbbc45f3aea8748445
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 6 02:44:34 2023 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Thu Jul 6 03:30:55 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ffdd99b0
dev-python/python-engineio: Bump to 4.5.0
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/python-engineio/Manifest | 1 +
.../python-engineio/python-engineio-4.5.0.ebuild | 53 ++++++++++++++++++++++
2 files changed, 54 insertions(+)
diff --git a/dev-python/python-engineio/Manifest b/dev-python/python-engineio/Manifest
index 0b773e63d3b5..df84f1961137 100644
--- a/dev-python/python-engineio/Manifest
+++ b/dev-python/python-engineio/Manifest
@@ -1,2 +1,3 @@
DIST python-engineio-4.4.0.gh.tar.gz 309353 BLAKE2B 4cf40802fddcce2e53e205bdbe73bdf0ec822e15581fe4a9939b8d05c3eb6ba82a99d089d4708169b197aa79e5b5f14001ff86f72025fc6d96c99ed6d73fe620 SHA512 b7995aaf2583ec58ac87f048608653ade3846dd103616ee90b3dc12cc7e27c7d37959cd3e1ebf6e138395ff6fad8cd011407b6660258715e513bf72c8a3e1f6f
DIST python-engineio-4.4.1.gh.tar.gz 309475 BLAKE2B 4ae5dd9887f4d3a70d4983d2a0f0de29b1a54d30961bfc430b8850ff4af73fa1cd9abad6caeb8248a44def42b02e26ecb0632dd9b4d57e2a7f44b33762659304 SHA512 a903ae4f5a4679f6d46fda09901b637ef8dcf2896ece8781460d27aab7c8da606e16a89ac5dea94c156d8196a7e931626b2310b41ddc61d4241b5e004ad2ca64
+DIST python-engineio-4.5.0.gh.tar.gz 309771 BLAKE2B ab58972ac543386c0254f6fe65041a88f6046312f7eac904128244b18a64107de174466b8934c9c6a51004c7614d199f1fd8362d816fdf8912cec29eddfc036b SHA512 3066fd2d3a3fc819318c4bd862c593e00012a29670ff76dbe926eae47c5ddd7a7483f16dedd9ef937d879f0533bff9eff4aee61ad4279651b39704722fac613b
diff --git a/dev-python/python-engineio/python-engineio-4.5.0.ebuild b/dev-python/python-engineio/python-engineio-4.5.0.ebuild
new file mode 100644
index 000000000000..705b082df961
--- /dev/null
+++ b/dev-python/python-engineio/python-engineio-4.5.0.ebuild
@@ -0,0 +1,53 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=setuptools
+PYTHON_COMPAT=( python3_{10..11} )
+
+inherit distutils-r1
+
+DESCRIPTION="Python implementation of the Engine.IO realtime server"
+HOMEPAGE="
+ https://python-engineio.readthedocs.io/
+ https://github.com/miguelgrinberg/python-engineio/
+ https://pypi.org/project/python-engineio/"
+SRC_URI="
+ https://github.com/miguelgrinberg/python-engineio/archive/v${PV}.tar.gz
+ -> ${P}.gh.tar.gz
+"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND="
+ dev-python/aiohttp[${PYTHON_USEDEP}]
+ dev-python/requests[${PYTHON_USEDEP}]
+ dev-python/websocket-client[${PYTHON_USEDEP}]
+"
+# Can use eventlet, werkzeug, or gevent, but no tests for werkzeug
+BDEPEND="
+ test? (
+ dev-python/tornado[${PYTHON_USEDEP}]
+ dev-python/websockets[${PYTHON_USEDEP}]
+ )
+"
+
+distutils_enable_tests pytest
+distutils_enable_sphinx docs \
+ dev-python/alabaster
+
+EPYTEST_IGNORE=(
+ # eventlet is masked for removal
+ tests/common/test_async_eventlet.py
+)
+
+EPYTEST_DESELECT=(
+ # also eventlet
+ tests/common/test_server.py::TestServer::test_async_mode_eventlet
+ tests/common/test_server.py::TestServer::test_connect
+ tests/common/test_server.py::TestServer::test_service_task_started
+ tests/common/test_server.py::TestServer::test_upgrades
+)
next reply other threads:[~2023-07-06 3:31 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 3:31 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-16 4:54 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-engineio/ Michał Górny
2024-10-14 4:11 Michał Górny
2024-06-30 17:00 Michał Górny
2024-06-30 17:00 Michał Górny
2024-05-19 6:02 Michał Górny
2024-02-26 14:25 Michał Górny
2024-02-06 3:07 Michał Górny
2024-01-07 6:16 Michał Górny
2023-12-30 18:32 Michał Górny
2023-12-29 4:38 Michał Górny
2023-12-29 4:38 Michał Górny
2023-11-23 20:11 Michał Górny
2023-10-15 3:26 Michał Górny
2023-09-14 17:21 Arthur Zamarin
2023-09-13 15:47 Michał Górny
2023-09-04 2:48 Michał Górny
2023-08-23 19:25 Michał Górny
2023-08-21 16:45 Michał Górny
2023-08-21 16:44 Michał Górny
2023-07-24 11:33 Michał Górny
2023-07-06 3:31 Michał Górny
2023-04-20 3:12 Michał Górny
2023-04-09 7:44 Arthur Zamarin
2023-04-08 6:08 Michał Górny
2023-03-17 5:32 Michał Górny
2022-11-17 18:07 Michał Górny
2022-10-21 14:34 Michał Górny
2022-10-21 14:34 Michał Górny
2022-08-04 17:55 Arthur Zamarin
2022-07-05 6:07 Michał Górny
2022-05-13 15:00 Michał Górny
2022-04-29 4:05 Sam James
2022-04-28 4:05 Sam James
2022-04-24 17:47 Arthur Zamarin
2022-04-24 17:47 Arthur Zamarin
2022-01-11 18:03 Arthur Zamarin
2021-10-27 8:29 Michał Górny
2021-10-17 9:25 Michał Górny
2021-08-02 5:44 Michał Górny
2021-05-15 21:18 Michał Górny
2021-04-16 8:30 Michał Górny
2021-03-11 12:55 Sam James
2021-03-11 12:55 Sam James
2021-03-11 12:24 Michał Górny
2021-03-11 8:48 Michał Górny
2020-04-22 1:20 Zac Medico
2020-04-22 1:17 Zac Medico
2020-03-28 21:11 Michał Górny
2020-02-05 20:47 Michał Górny
2018-07-03 21:54 Zac Medico
2018-04-13 9:53 Zac Medico
2017-09-24 23:08 Zac Medico
2017-05-03 7:37 Michał Górny
2017-04-28 18:35 Zac Medico
2017-04-28 4:15 Zac Medico
2017-03-15 8:36 Zac Medico
2017-01-26 4:09 Zac Medico
2016-10-12 6:49 Zac Medico
2016-10-12 6:49 Zac Medico
2016-06-29 18:18 Patrick Lauer
2016-03-12 11:40 Patrick Lauer
2016-02-27 0:49 Zac Medico
2016-01-12 0:38 Zac Medico
2015-12-22 21:49 Zac Medico
2015-12-07 21:15 Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1688614255.ffdd99b0f4d1467a7aa943bbbc45f3aea8748445.mgorny@gentoo \
--to=mgorny@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox