Skip to content
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

Fails to build with python 3.8 beta 2 (3.8.0b2) #1455

Closed
gicmo opened this issue Jul 12, 2019 · 6 comments
Closed

Fails to build with python 3.8 beta 2 (3.8.0b2) #1455

gicmo opened this issue Jul 12, 2019 · 6 comments
Labels
Bug A crash, misbehaviour, or other problem Unresolved Waiting for a fix or implementation

Comments

@gicmo
Copy link
Contributor

gicmo commented Jul 12, 2019

Fedora 32 will switch (ChangeProposal to Python 3.8). The latter should be release around 2019-10-21 (3.8 schedule). Currently (1.4) the build fails because the custom swig (swig-modified-6) generates code that uses a deprecated symbol that got removed in 3.8 (_PyObject_GC_UNTRACK). I included a patch in the Fedora rpm to make it compile. It seems that upstream builtin.swg#L120@master also still uses that marco (_PyObject_GC_UNTRACK), so just updating swig will (for now) to solve the issue. Maybe that will change until Python 3.8 is released.

@baldurk
Copy link
Owner

baldurk commented Jul 12, 2019

(Assuming you meant that "updating swig will (for now) not solve the issue"). I'm already pretty committed to maintaining the swig fork indefinitely, so applying that patch should be fine I think. Since this is only in the .swg files it's pretty easy to update, I'll just need to bump the swig fork's version which is a bit tedious.

@baldurk baldurk added Bug A crash, misbehaviour, or other problem Unresolved Waiting for a fix or implementation labels Jul 12, 2019
@gicmo
Copy link
Contributor Author

gicmo commented Jul 12, 2019

@baldurk ah yes, sorry, indeed meant "not solve the issue". This is not super urgent because we have some time until 3.8 is released but I wanted this to be on the radar. Just for the record, the docu for _PyObject_GC_UNTRACK stating "Deprecated since version 3.6: This macro is removed from Python 3.8.". I am a bit puzzled but I don't even see an issue for that on the swig repo.

@gicmo
Copy link
Contributor Author

gicmo commented Jul 12, 2019

I filed a issue swig#1586 and submitted a PR #1587, with a patch that should also be backwards compatible.

@baldurk
Copy link
Owner

baldurk commented Jul 12, 2019

You might be waiting a while, from what I saw before swig isn't a very responsive project. Either way I'll need to manually backport it so I'll take your patch directly whether or not it's merged upstream.

@gicmo
Copy link
Contributor Author

gicmo commented Jul 18, 2019

Upstream took the patch 🎉, since they only support 2.7 and >= 3.2 they even went for the simpler version, which is identical code-wise with the patch I stuck in the RPM. Want me to file a PR against renderdoc's custom swig repo?

@baldurk
Copy link
Owner

baldurk commented Jul 22, 2019

I merged your patch into the branch manually because it can be a bit of a pain to handle the swig fork. I've also updated the tag with that commit above. Thanks for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A crash, misbehaviour, or other problem Unresolved Waiting for a fix or implementation
Projects
None yet
Development

No branches or pull requests

2 participants