Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork31
Fix different linkage error with cp313-win#136
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
/CC@vstinner |
This issue should be fixed by the changec84545f : can you please try the fix in mypy CI? |
Thanks! My test setup looks fine. Openedpython/mypy#18560 for mypy. |
Oh! I misread this pull request. I saw it as an issue and I wrote exactly the same fix :-D Sorry, I could merge your PR directly. |
It's fixed now.https://github.com/mypyc/mypy_mypyc-wheels/actions/runs/13014956712/job/36301735749 |
Thabks again for your bug report and your fix@cdce8p! |
Seems there was one another regression. Our the
cp313-win
wheel build started to fail after thepythoncapi_compat.h
update was merged.We don't test every platform version combination in CI, that's why I missed it initially.Seems like a similar issue to#115 where MSVC requires that the signatures match the upstream ones exactly.
Also updated
_Py_fopen_obj
even though that didn't fail for us. Probably just because we don't usePy_fopen
yet.