Skip to content

Fixed issue with pypy 3.11 and latest crypt4gh - #284

Open
jmfernandez wants to merge 5 commits into
mainfrom
240-allow-killing-jobs-from-command-line
Open

Fixed issue with pypy 3.11 and latest crypt4gh#284
jmfernandez wants to merge 5 commits into
mainfrom
240-allow-killing-jobs-from-command-line

Conversation

@jmfernandez

Copy link
Copy Markdown
Member

Latest crypt4gh release is not pre-compiled for pypy 3.11. When pip tries compiling it from its source wheel stored at pypi, it fails preparing the compilation of a static copy of libsodium used by it, because it lacks some expected files. So, for pypy, the source of crypt4gh is switched to its github repo.

jmfernandez and others added 5 commits July 28, 2026 00:24
…straints

Updated constraints due security reasons (triggered on 2026-07-27T22:30:39+00:00 by 8aac49f)
`black` is written in Python, and latest releases do not work on
discontinued Python versions. As upstream also releases `black` as
a self-contained, pre-compiled binary, switch to that both at the
pre-commit and development dependencies.

The main problem we have had in the past trying to support several
versions of black is that the formatting rules evolve on each release,
so what it is considered ok in an ancient release must be reformatted
with newer ones. So, we were adhering to an ancient release which
was supporting Python 3.7.

The problems started when we added support for Python 3.14, as
the old version of black did not work on that python release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant