-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Disabling PyPy #201
Comments
Admittedly this may be less of an issue given we were able to move to |
If you opt out then downstream packages that need pypy and dask have no choice. Mark the prs as drafts. |
Think we added PyPy previously ( #155 ). So Idk if there is a way to back that out as it were |
This might also be tied to accendental merges of PRs for migrations: |
Is supporting pypy such a burden that it is worth actively blocking? Has it caused problems? |
@mattip probably better to have that discussion in issue ( dask/distributed#5681 ) |
to be honest. with the pypy38 migration, now might be the best time to simply delete the yaml file. |
Users will still be able to use the old version. |
It's just that there haven't been any known users, and we're trying to be a
little bit more focused. There's a question that arises of "would this
affect PyPy users?" that we'd prefer not to have to think about.
…On Wed, Mar 30, 2022 at 3:44 PM Matti Picus ***@***.***> wrote:
Is supporting pypy such a burden that it is worth actively blocking? Has
it caused problems?
—
Reply to this email directly, view it on GitHub
<#201 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTEDGSYL7MCPVEIEIMTVCS4I7ANCNFSM5SDBDU4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Recently the Dask Community decided to drop PyPy support. Given this, what is the best way for us to disable PyPy support? We can add a
skip
to the recipe to disable these builds.Though as discussed in issues ( regro/cf-scripts#1044 ) ( regro/cf-scripts#1386 ), we don't have a great way to opt-out of migrations and this can have downstream effects.
Given this, am raising this issue to solicit feedback ( cc @conda-forge/core ) on how we should handle this here and the proceed with next steps.
cc @jrbourbeau @mrocklin
The text was updated successfully, but these errors were encountered: