-
Notifications
You must be signed in to change notification settings - Fork 119
"broken" since go 1.21 #370
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
Comments
Interesting, I could have sworn I had gopy working on go 1.24.1, I recall needing to install go with brew as being on the right arch was important (for apple silicon, that is). I can't get the example to even build, there is a depreciated build flag. Setup under a venv:
Build fails with
Full log below. Note: I passed the full python venv path as not doing that can break things.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I say "broken" because according to the golang issue this was never intended to work and was merely working by accident: golang/go#65050 (comment)
here's a small reproduction demoing this breakage. I'm running on macos x86_64 which seems to be the most reliable to reproduce for some reason I don't completely understand:
setup:
reproduction
here's a small python script using the compiled output:
(all that really needs to be involved is >1 extension in the same process)
boom
(and sometimes the crash is in various other places -- this just seems to be the most common one)
aside: I decided to abandon setuptools-golang for this reason 🤷 -- and yeah a clickbaitish video with more details
The text was updated successfully, but these errors were encountered: