mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Markus Heidelberg via ptxdist <ptxdist@pengutronix.de>
To: <ptxdist@pengutronix.de>
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: [ptxdist] [PATCH 0/5] Add Flask package and missing dependencies
Date: Fri, 23 May 2025 13:49:46 +0200	[thread overview]
Message-ID: <20250523114951.1747739-1-m.heidelberg@cab.de> (raw)

Flask is a lightweight WSGI web application framework.

After having finished and tested the packages, before submission to
PTXdist I wanted to update to the latest versions that had been released
in the meantime.
For flask and click there were newer versions available, but they caused
build errors due to changed 'license' keyword type in pyproject.toml. An
update to flit-core >= 3.11.0 would have been required, but I wasn't
sure about possible side-effects so i decided to leave it as is.

See also:
https://flit.pypa.io/en/latest/history.html#version-3-11
https://github.com/pypa/flit/commit/640b6ad973e406b352649d36eb35dc208ecbb0ca

Markus Heidelberg (5):
  python3-werkzeug: new package
  python3-click: new package
  python3-blinker: new package
  python3-itsdangerous: new package
  python3-flask: new package

 rules/python3-blinker.in        | 11 +++++++
 rules/python3-blinker.make      | 56 +++++++++++++++++++++++++++++++
 rules/python3-click.in          | 11 +++++++
 rules/python3-click.make        | 56 +++++++++++++++++++++++++++++++
 rules/python3-flask.in          | 17 ++++++++++
 rules/python3-flask.make        | 58 +++++++++++++++++++++++++++++++++
 rules/python3-itsdangerous.in   | 11 +++++++
 rules/python3-itsdangerous.make | 56 +++++++++++++++++++++++++++++++
 rules/python3-werkzeug.in       | 11 +++++++
 rules/python3-werkzeug.make     | 56 +++++++++++++++++++++++++++++++
 10 files changed, 343 insertions(+)
 create mode 100644 rules/python3-blinker.in
 create mode 100644 rules/python3-blinker.make
 create mode 100644 rules/python3-click.in
 create mode 100644 rules/python3-click.make
 create mode 100644 rules/python3-flask.in
 create mode 100644 rules/python3-flask.make
 create mode 100644 rules/python3-itsdangerous.in
 create mode 100644 rules/python3-itsdangerous.make
 create mode 100644 rules/python3-werkzeug.in
 create mode 100644 rules/python3-werkzeug.make

-- 
2.43.0




             reply	other threads:[~2025-05-23 11:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 11:49 Markus Heidelberg via ptxdist [this message]
2025-05-23 11:49 ` [ptxdist] [PATCH 1/5] python3-werkzeug: new package Markus Heidelberg via ptxdist
2025-06-03 10:38   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-05-23 11:49 ` [ptxdist] [PATCH 2/5] python3-click: " Markus Heidelberg via ptxdist
2025-06-03 10:38   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-05-23 11:49 ` [ptxdist] [PATCH 3/5] python3-blinker: " Markus Heidelberg via ptxdist
2025-06-03 10:38   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-05-23 11:49 ` [ptxdist] [PATCH 4/5] python3-itsdangerous: " Markus Heidelberg via ptxdist
2025-06-03 10:38   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-05-23 11:49 ` [ptxdist] [PATCH 5/5] python3-flask: " Markus Heidelberg via ptxdist
2025-06-03 10:39   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20250523114951.1747739-1-m.heidelberg@cab.de \
    --to=ptxdist@pengutronix.de \
    --cc=m.heidelberg@cab.de \
    /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