RE: python-cryptography >= 3.4.0 and Rust

[Allen Hewes <allen@decisiv.com>]

> -----Original Message-----
> From: Cygwin-apps <cygwin-apps-bounces+allen=decisiv.com@cygwin.com>
> On Behalf Of Marco Atzeri
> Sent: Friday, February 4, 2022 1:52 AM
> To: cygwin-apps@cygwin.com
> Subject: Re: python-cryptography >= 3.4.0 and Rust
>
> On 03.02.2022 23:11, Allen Hewes wrote:
> > Hi @all,
> >
> > I use Cygwin pretty much like Linux in/on my Windows machines. Meaning,
> I am not using it for POSIX reasons. I do like Cygwin a lot, I prefer Cygwin over
> WSL/WSL2.
> >
> > A PyPI package I wanted to use has a hard dependency on
> cryptography>=35.0.
> >
> > So I downloaded the Cygwin source for python-cryptography and got to
> work on updating it to 35.0.
> >
> > Welp, then the wheels came off. I am assuming that Cygwin's python-
> cryptography is still at 3.3.2 b/c of this Rust issue?
> >
>
> Hi Allen,
> it is correct. I released the last version that was still on C
>

It's still on C but the authors have been adding new features in Rust. They are using the Python Rust API bridge for the integration between the two.

> > Rust is making more in-roads into software I use frequently or like to use. Is
> there any efforts or discussions about getting Rust able to target Cygwin?
>
> Not that I aware of.
> We have already problem to update clang that is already behind.
>

Many of the shiny new sysadmin/sysutils are written in Rust or Go.

The reason why I brought up python cryptography and Cygwin is that the current version of python cryptography doesn't support OpenSSL 3 (AFAIK). Only the most recent cryptography does. At some point in the future, this will have to be addressed, wouldn't it (IMHO)? Python cryptography is fundamental in the Python ecosystem. Pythonistas who use Cygwin will need an update to cryptography. How can this happen?

> Rust and Go are purely wish, they both requires specific expertize and time.
>

...except for then those languages make in-roads into the bits/ecosystem that Cygwin has packaged/supported (for a long time in some cases). From what I can tell, these ecosystems think WSL/WSL2 is their "best effort" for Linux-y (or POSIX) on Windows.

> Feel free to work on it

Based on the conversation in rigrep (a Rust grepper), it sounds like it's a large amount of work that would not be accepted/entertained by upstream:
https://github.com/BurntSushi/ripgrep/issues/269

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.