From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: python-cryptography >= 3.4.0 and Rust
Date: Fri, 4 Feb 2022 07:52:18 +0100 [thread overview]
Message-ID: <c0a74a44-b1f4-c51a-ad12-b521063c20a8@gmail.com> (raw)
In-Reply-To: <MN2PR17MB3999D4DB301FC89CE4D8703FB8289@MN2PR17MB3999.namprd17.prod.outlook.com>
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
> 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.
Rust and Go are purely wish, they both requires specific expertize
and time.
Feel free to work on it
> Thanks,
>
> /allen
Regards
Marco
next prev parent reply other threads:[~2022-02-04 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 22:11 Allen Hewes
2022-02-04 6:52 ` Marco Atzeri [this message]
2022-02-04 15:28 ` Allen Hewes
2022-02-04 21:28 ` Marco Atzeri
2022-02-07 4:02 ` Allen Hewes
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=c0a74a44-b1f4-c51a-ad12-b521063c20a8@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).