-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
patch for _Py_fopen -> fopen #110
Conversation
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 ( |
@conda-forge-admin, please rerender |
…da-forge-pinning 2021.01.20.17.38.08
They can't be replaced, unless you copy the |
ahh. So what happens to those PRs if this gets merged? |
They'll have to be rebased. |
@conda-forge-admin, rerender |
…da-forge-pinning 2021.01.20.17.38.08
Nope. boost is using internal structures
|
Deeper into the rabbit hole: on latest HEAD that problem is gone. It was fixed in boostorg/python#291 |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
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)Adopt upstream boostorg/python#344. Should be enough to get the PyPy3.7 migration to pass.