-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Segfault with black 22.1.0 #2845
Comments
Thanks for reporting this! I don't have time to investigate in detail right now, but here's a few things that anyone reading this could do to help:
|
I recommend using |
Thanks for the suggestion. I can confirm that |
python/mypy#12605 reports this bug upstream - |
Can reproduce with |
python/mypy#13152 fixes this, but it hasn't made its way into a mypy release yet. The next release is being tracked in python/mypy#13385 but it seems to be behind schedule (as usual for mypy). Once mypy cuts a new release I'll upgrade our mypy[c] cibuildwheel requirement, resolving this. |
Any updates on this? |
The latest release, 22.12.0, was made with mypy 0.991, but for unrelated reasons we don't have MacOS mypyc wheels. |
Black 23.1.0 no longer runs into this segfault as it was built using mypy(c) 0.991. Interestingly Black 22.12.0 still segfaulted... I'm on Linux with a CPython 3.11 debug build for what it's worth. |
Ah, we bumped mypy(c) the day after 22.12.0 was cut.
|
Describe the bug
When running black with a self-built Python 3.10 I get a segfault.
To Reproduce
Can be reproduced in Docker:
Pipfile
:Then running black leads to a segfault error
Expected behavior
Black should not lead to a segfault.
Environment
** Further remarks **
Curiously, I could run the tests as instructed without errors.
The text was updated successfully, but these errors were encountered: