From: Anna <cyber+gentoo@sysrq.in>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [gentoo-dev] Rust is here to eat your Pythonz
Date: Tue, 26 Jul 2022 14:49:17 +0500 [thread overview]
Message-ID: <Yt+4nQgr4rgeUyLY@sysrq.in> (raw)
In-Reply-To: <19ec63ff438cbae29877d1b026699df797b9eefe.camel@gentoo.org>
On 2022-07-26 08:42, Michał Górny wrote:
> Hi, everyone.
>
> Just a quick FYI: since Rust is going to be marked stable on the last
> architecture (sparc) that it's going to support in Gentoo, we're going
> to start cleaning up old dev-python/cryptography soon. If you don't
> want Rust, removing cryptography entirely will be your only option.
I see three solutions here (except installing rust):
1) Stick to old cryptography/pyopenssl (if none of vulnerabilities
impact revdeps)
2) Kindly ask upstream to switch to PyCryptodome
3) Write a library that implements cryptography API using PyCryptodome
The last option is kinda useless but fun. If you find it interesting,
contact me.
parent reply other threads:[~2022-07-26 9:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <19ec63ff438cbae29877d1b026699df797b9eefe.camel@gentoo.org>]
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=Yt+4nQgr4rgeUyLY@sysrq.in \
--to=cyber+gentoo@sysrq.in \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-user@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