Conversation
I guess the question is who is "you"? I think this repo was started by @antocuni before cibuildwheel, github actions, and conda supported PyPy as a way to bootstrap c-extension wheel building. At some point cibuildwheel maintainers became the ones pushing PRs. So if cibuildwheel does not need this repo, perhaps it should be archived. There is also https://github.com/docker-library/pypy who maintain a docker image with pypy installed. |
Myeah, I was wondering if the images were still used internally by PyPy or in other projects. But I'll take it that's a no, then?
Normally, cibuildwheel should be fine now, but maybe we should wait another release to see how smoothly things go? But all in all, I guess it's good news about PyPy adoption, if it's included in a bunch of external images and environments! :-) |
|
I think that the main user for these docker images is my repo https://github.com/antocuni/pypy-wheels/ but admittedly I haven't updated it for a while and I don't plan to do any work on it. I don't know if there are any other users of these docker images though. |
Quick, minor update, but with a twist: this time, we don't really need it for cibuildwheel, as pypa/manylinux#1103 happened.
So, question: do you still wish to receive future PRs with updates for the image?
The new manylinux images only contain PyPy 7.3.5 Python 3.7, right now. So, this repository/image contains still contains extra:
If none of these are still necessary, or it is good enough to have these older Docker images for now, having everything in PyPA's manylinux images is of course a great advantage. If you would like to keep these images as well, then I can do my best to remind myself and keep providing PRs (and test then with cibuildwheel).