Re: rust and python
Jon Turney via Cygwin-apps <[email protected]> Mon, 2 Mar 2026 13:50:50 +0000
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Message-ID | <[email protected]> |
On 02/02/2026 06:33, Marco Atzeri via Cygwin-apps wrote: > On 01/02/2026 22:59, Jon Turney via Cygwin-apps wrote: >> On 06/01/2026 11:21, Christoph Reiter via Cygwin-apps wrote: >>> Not sure if this is the cause here, but maturing defaults to >>> "cygwin_86_64" because of me since >>> https://github.com/PyO3/maturin/pull/2819 >>> I suggested on this list some months ago to change sysconfig to match >>> it like: https://gist.github.com/lazka/c8146c08c0ebe5beb43b6ffb6c2ae51b >>> so pip stays happy across cygwin DLL updates >> >> Thanks for the link. >> >> I added an extra bit of reporting in the latest version of cygport so >> it reports the wheel filename it's choking on: >> >>> Installing python-cryptography-46.0.3-1.x86_64 >>> *** Info: installing 3.9 >>> *** ERROR: unknown wheel filename: cryptography-46.0.3-cp312-abi3- >>> cygwin_86_64.whl >> >> I'm kind of confused where the 'x' in 'x86_64' has gone here? >> >> That seems kind of wrong to me -'86_64' isn't the name of anything. >> >> But I thought anyhow, I should just change cygport to accept that, but >> currently, if we try to feed that wheel name into 'pip install', it >> fails with: >> >>> ERROR: cryptography-46.0.3-cp39-abi3-cygwin_86_64.whl is not a >>> supported wheel on this platform. >> >> ... so I'm not sure what's supposed to be happening here. >> > > It is python rejecting it. Indeed. With that overly-prescriptive check on the wheel filename disabled in cygport: > $ cygport python-cryptography.cygport all >>>> Preparing python-cryptography-46.0.3-1.x86_64 >>>> Unpacking source cryptography-46.0.3.tar.gz >>>> Preparing working source directory >>>> Compiling python-cryptography-46.0.3-1.x86_64 > *** Info: building 3.9 > Processing ./. > Preparing metadata (pyproject.toml): started > Preparing metadata (pyproject.toml): finished with status 'done' > Building wheels for collected packages: cryptography > Building wheel for cryptography (pyproject.toml): started > Building wheel for cryptography (pyproject.toml): still running... > Building wheel for cryptography (pyproject.toml): finished with status 'done' > Created wheel for cryptography: filename=cryptography-46.0.3-cp39-abi3-cygwin_86_64.whl size=2390885 sha256=51a667a083bc830f548621a94028851f397cac050261ffb8c5d5e2feab1223e1 > Stored in directory: /tmp/pip-ephem-wheel-cache-dlflshcs/wheels/b6/b3/32/6fdb21abd3a0326a1c54156f0baaff9082c452761a71694d2a > Successfully built cryptography [...] >>>> Installing python-cryptography-46.0.3-1.x86_64 > *** Info: installing 3.9 > ERROR: cryptography-46.0.3-cp39-abi3-cygwin_86_64.whl is not a supported wheel on this platform. > *** ERROR: pip3.9 install failed The "not a supported wheel" error comes from 'pip install'. As Marco notes, you can work around this by renaming the .whl file to the expected form. So, I don't quite understand how this works on msys2? Is there some other change needed elsewhere? Or are we installing wheels the wrong way?