From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Flask: update to 3.0, clean up stale dependants
Date: Tue, 24 Oct 2023 15:35:46 +0200 [thread overview]
Message-ID: <20231024133546.ooqp2QmFHT1RLP9irpOsFmcYa40IM4ElC3aP5JAcceo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46736@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
There's a closed pull request on the void-packages repository
Flask: update to 3.0, clean up stale dependants
https://github.com/void-linux/void-packages/pull/46736
Description:
Flask and Werkzeug 3 drop some deprecated interfaces and break some old packages, but a lot of these are effectively dead anyway.
## Testing the changes
- I tested the changes in this PR: **in progress**
The results of `xbps-src` check on the dependants of `python3-Flask` and `python3-Werkzeug` are noted below.
### Flask dependants
- [ ] etesync-dav (no tests; version restrictions on Flask-WTF have been violated since 2022-09-07)
- [ ] mkchromecast (no tests, maybe abandonware)
- [ ] python3-Flask-HTTPAuth (no tests)
- [ ] python3-Flask-RESTful (tests are broken with Python 3.12)
- [ ] voltron (test framework uncertain)
- [x] OpenLP (23 pre-existing failures, 17 pre-existing errors)
- [x] fava (4 pre-existing failures)
- [x] grip
- [x] impacket (1396 pre-existing failures)
- [x] mitmproxy (3 pre-existing failures)
- [x] python3-Flask-Babel
- [x] python3-Flask-Cors
- [x] python3-Flask-Login
- [x] python3-Flask-WTF
- [x] python3-httpbin
### Werkzeug Dependants
- [x] python3-openapi-core
- [x] python3-pytest-httpserver
- [x] python3-pytest-localserver
- [x] python3-quart
## Removed Packages
- python3-Flask-User
- python3-Flask-Mail
- python3-Flask-Script
- python3-Flask-OAuthlib
- python3-Flask-Assets
- python3-Flask-SQLAlchemy
- python3-stormssh
prev parent reply other threads:[~2023-10-24 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:23 [PR PATCH] [WIP] " ahesford
2023-10-16 20:37 ` [PR PATCH] [Updated] " ahesford
2023-10-17 12:24 ` ahesford
2023-10-17 14:04 ` ahesford
2023-10-17 14:14 ` ahesford
2023-10-17 14:20 ` [PR PATCH] [Updated] " ahesford
2023-10-24 13:35 ` ahesford [this message]
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=20231024133546.ooqp2QmFHT1RLP9irpOsFmcYa40IM4ElC3aP5JAcceo@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).