Skip to content

Commit 77d5634

Browse files
authored
Merge pull request #2259 from h-vetinari/byebye_pypy
Add announcement for sunsetting PyPy
2 parents 5c2212f + 469f320 commit 77d5634

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed

news/2024-08-14-sunsetting-pypy.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Sunsetting PyPy support
2+
3+
TL;DR: We are planning to remove PyPy from conda-forge feedstock recipes in a
4+
few weeks (and thus to stop building new releases of packages for PyPy), unless
5+
there is substantial enough interest to justify the continued maintenance effort.
6+
7+
<!-- truncate -->
8+
9+
Conda-forge introduced [support](https://conda-forge.org/blog/2020/03/10/pypy/)
10+
for [PyPy](https://pypy.org/index.html) as an alternative implementation of
11+
Python about 4.5 years ago.
12+
13+
In that time we have worked hard together with developers from PyPy to provide
14+
easily installable pre-compiled builds of the most common libraries also for PyPy.
15+
16+
As a very positive side-effect, the infrastructure of conda-forge is now fully
17+
equipped to deal with alternative implementations of the Python interpreter,
18+
which will continue to be useful (for example for supporting the experimental
19+
free-threading builds of CPython 3.13).
20+
21+
However, due to a lack of resources – both in terms of expertise for PyPy, as
22+
well as available time of those who can help – the conda-forge builds for PyPy
23+
packages have been in minimal maintenance for a while (for example, we never
24+
migrated for PyPy 3.10, nor did PyPy participate in the NumPy 2.0 migration).
25+
26+
As a consequence, we unfortunately need to announce that we are sunsetting
27+
support for PyPy. This means we will stop the long-running migrator to add
28+
PyPy to new feedstocks, and we will begin removing PyPy builds from feedstocks
29+
at the latest on October 1st, or when we begin migrating for CPython 3.13
30+
(whichever comes earlier).
31+
32+
If you are depending on PyPy builds in some way, please let us know about the
33+
specifics of your situation in the discussion issue for the
34+
[RFC](https://github.com/conda-forge/conda-forge.github.io/issues/2255).
35+
36+
There is a possibility that we receive the necessary support from the PyPy
37+
developers, if it turns out that enough people depend on PyPy support in
38+
conda-forge for it to be worth their time. As such, please speak up if you
39+
fall into this category!
40+
41+
Finally, no matter the outcome, we want to congratulate the PyPy developers
42+
for their important contributions and exploration of what is possible in the
43+
Python ecosystem! 👏
44+
45+
It has been a pleasure to collaborate!

0 commit comments

Comments
 (0)