From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [Python-Dev] Move support of legacy platforms/architectures outside Python
Date: Mon, 22 Feb 2021 09:30:28 +0100 [thread overview]
Message-ID: <5b43f12e17ee17add9729dd42dd211ada87638b6.camel@gentoo.org> (raw)
In-Reply-To: <f3b35ead-dbcf-d2fd-a676-8d16dd6196ea@gentoo.org>
On Sun, 2021-02-21 at 20:32 -0500, Joshua Kinard wrote:
> On 2/21/2021 08:01, Michał Górny wrote:
> > Hi,
> >
> > FYI, a few member of Python upstream are continuing their crusade
> > against minor architectures not supported by Rust. This time, they're
> > discussing actively removing support for platforms they don't officially
> > support, and requiring people to maintain external patches forever.
>
> In case I missed something, what is the intersection here between Rust and
> Python? Is it just the Python devs taking a page out of Rust's guidebook on
> platform/arch support, or is there some change coming down the road, like
> where Python will be re-written in Rust?
It's the context/timing. Cryptography starts being rewritten in Rust.
I report a bug that this breaks platforms not supported by Rust [1].
Suddenly a few core Python developers appear and applaud the effort,
indicating that Python does not support these arches.
In middle of this, one of the Python devs proposes removing s390
support. The patch [2] does not remove any real code that could burden
developers -- it just demolishes some places to break the support.
The request receives negative feedback.
So now we have suddenly the crusade against all 'unsupported'
architectures, to justify the crusade.
I don't know whether Python will actually be rewritten in Rust or start
depending on Rust packages but it's not impossible. However, it's
pretty clear that the whole discussion was triggered by the Rust rewrite
of cryptography.
As for your other comments, I can't really comment on them.
[1] https://github.com/pyca/cryptography/issues/5771
[2] https://github.com/python/cpython/pull/24534
[3] https://bugs.python.org/issue43179
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2021-02-22 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABqyc3zVU0rLzcPA_vwdnDp3oKLP0HnMuDN6VNPwWpfY-X38hQ@mail.gmail.com>
2021-02-21 13:01 ` [gentoo-dev] Fwd: [Python-Dev] Move support of legacy platforms/architectures outside Python Michał Górny
2021-02-21 13:28 ` Aisha Tammy
2021-02-22 1:32 ` Joshua Kinard
2021-02-22 8:30 ` Michał Górny [this message]
2021-02-23 6:16 ` Alec Warner
2021-02-23 8:11 ` Michał Górny
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=5b43f12e17ee17add9729dd42dd211ada87638b6.camel@gentoo.org \
--to=mgorny@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