From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python3, python2: clean up templates and dead alternatives, combine python2 and python2-tkinter
Date: Sun, 09 Feb 2025 04:58:03 +0100 [thread overview]
Message-ID: <20250209035803.8BD6329D3C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54161@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
There's a closed pull request on the void-packages repository
python3, python2: clean up templates and dead alternatives, combine python2 and python2-tkinter
https://github.com/void-linux/void-packages/pull/54161
Description:
The `2to3` script is gone in our `python3`, making the `2to3` alternative obsolete. The `idle` alternative in the main `python3` package is wrong, because it produces a dead symlink when `idle-python3` is not installed.
Rather than split off a new `idle` alternative that behaves properly, it's better to just make a fixed `idle` symlink in the `idle-python3` package, drop `idle` from the `python` alternative in the `python2` package, and move on. This means that py2 users will have to use `idle2` or `idle2.7`, but we shouldn't worry about that anymore. It's a dead package that is already marked for "limited use".
At the same time, we don't have to worry about cycles with `python2`, so we can drop the split package and build the whole thing together.
Eventually, we should drop the alternatives for `python2` entirely, but that's a broader scope that I don't want to think about at the moment.
Closes: #54154.
cc: @leahneukirchen
next prev parent reply other threads:[~2025-02-09 3:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 17:04 [PR PATCH] python3, python2: clean up templates andgg " ahesford
2025-02-02 23:02 ` [PR REVIEW] " sgn
2025-02-02 23:02 ` sgn
2025-02-03 12:47 ` ahesford
2025-02-09 1:36 ` [PR PATCH] [Updated] python3, python2: clean up templates and " ahesford
2025-02-09 3:58 ` ahesford [this message]
2025-02-09 3:58 ` ahesford
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=20250209035803.8BD6329D3C@inbox.vuxu.org \
--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).