From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "James Hilliard" <james.hilliard1@gmail.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 0/2] package: add new python packages
Date: Tue, 10 Feb 2026 22:01:54 +0100 [thread overview]
Message-ID: <20260210-python-packages-v1-0-6153f56421d4@bootlin.com> (raw)
Hello,
this small series aims to introduce two new python packages:
- python-flask-socketio: allows event-based bi-directional
communication between Flask applications and server
- python-gevent: a coroutine-based network library, as a dependency of
python-flask-socketio
python-flask-socketio needs at least one of those dependencies:
- eventlet
- gevent
- flask dev server
[0] mentions that eventlet is discouraged for new projects, and [1]
states that Flask webserver should not be used for production, hence
this series selects gevent as the default dependency for
python-flask-socketio.
- The two packages have been generated with ./utils/scanpypi, and adjusted
accordingly (license, and build/runtime dependencies).
- Both packages bring a minimal test ensuring at least that the
corresponding import can be performed as well as basic
instantation/manipulation
- Both packages have been tested locally with ./utils/test-pkg, and
./support/testing/run-tests (through ./utils/docker-run)
[0] https://eventlet.readthedocs.io/en/latest/
[1] https://flask-socketio.readthedocs.io/en/latest/intro.html#requirements
Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
---
Alexis Lothoré (2):
package/python-gevent: new package
package/python-flask-socketio: new package
DEVELOPERS | 2 ++
package/Config.in | 2 ++
package/python-flask-socketio/Config.in | 14 ++++++++++++++
.../python-flask-socketio/python-flask-socketio.hash | 5 +++++
.../python-flask-socketio/python-flask-socketio.mk | 14 ++++++++++++++
package/python-gevent/Config.in | 19 +++++++++++++++++++
package/python-gevent/python-gevent.hash | 5 +++++
package/python-gevent/python-gevent.mk | 16 ++++++++++++++++
.../tests/package/sample_python_flask_socketio.py | 5 +++++
support/testing/tests/package/sample_python_gevent.py | 7 +++++++
.../tests/package/test_python_flask_socketio.py | 12 ++++++++++++
support/testing/tests/package/test_python_gevent.py | 12 ++++++++++++
12 files changed, 113 insertions(+)
---
base-commit: 94a817a58909e1cfe0c1f63b63754079f1866523
change-id: 20250804-python-packages-5e4a98a47c1d
Best regards,
--
Alexis Lothoré <alexis.lothore@bootlin.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-02-10 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 21:01 Alexis Lothoré via buildroot [this message]
2026-02-10 21:01 ` [Buildroot] [PATCH 1/2] package/python-gevent: new package Alexis Lothoré via buildroot
2026-02-10 21:01 ` [Buildroot] [PATCH 2/2] package/python-flask-socketio: " Alexis Lothoré via buildroot
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=20260210-python-packages-v1-0-6153f56421d4@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=james.hilliard1@gmail.com \
--cc=nicolas.carrier@nav-timing.safrangroup.com \
--cc=thomas.petazzoni@bootlin.com \
/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