-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pypy7.3.15 #116
Pypy7.3.15 #116
Conversation
…nda-forge-pinning 2023.12.24.07.24.16
…nda-forge-pinning 2023.12.24.07.24.16
…nda-forge-pinning 2024.01.26.23.27.14
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!
IIUC, pypy3.10 is blocked on (at least) pypy/pypy#4883? I saw the discussion in conda-forge/pypy-meta-feedstock#32 just now (wasn't following that repo), and I agree it would be good to have 3.10 even if we don't end up migrating for it1
Footnotes
-
though I guess I'd be tempted to migrate nevertheless, because - modulo some issues where testing got tightened (e.g. pandas) - it'd be almost "for free" to catch up with the "feedstock coverage" of the pypy3.9 migration. ↩
Nothing is ever for free. With only 1385 packages migrated and nearly 400 packages still in transit, the pypy38/39 migration is far from finished. I thought the 3.10 package would JustWork, and it seems there are problems, like pypy/pypy#4883 |
Reminder: once this gets merged, I should use this workflow to create and upload ppc64le and aarch64 packages |
My point was not about those in transit, but those already built for pypy3.9. Based on previous migrations and pypy's focus on compatibility, I expect the vast majority of feedstocks already being built for pypy3.9 to build essentially unchanged for pypy3.10 as well. That's what I meant by "catching up with the feedstock coverage". If indeed there is a lot of breakage by going from 3.9 and 3.10 (like apparently pypy/pypy#4883), then that argument is moot, but I think that should be rare. In any case, the migration discussion is completely separate, and just building 3.10 already would be cool. |
I uploaded the aarch64 and ppc64le packages to https://anaconda.org/mattip/pypy3.9/files and marked them as "copy". Here are the logs aarch64-log.txt @isuruf could you check the logs and copy the packages to the proper place? |
I just had a look, and I see that there are several builds in those logs (for aarch)
The last one matches what you uploaded, so I assume that's the correct log, but next time please only copy the logs for the respective build. The build logs itself look fine, though there's a bunch of noise coming from |
Sorry.
Yes. That can be confirmed in the py3.10 runs, which fail that test and is why I excluded 3.10 from this PR. |
Copied!
|
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Closes #115 (once the ppc64le build is uploaded manually)
Updates PyPy to 7.3.15, which replaces #114. Also creates a python3.10 package for pypy, which solves conda-forge/pypy-meta-feedstock#32. This is a convenience, and is not meant to trigger a migration. People who want to use python3.10 with PyPy will need to install packages from pip.