-
Notifications
You must be signed in to change notification settings - Fork 59
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 _sync()
methods on python 3.11
#138
Comments
OK. It looks like this is an issue in v0.2.3 but is working in the latest git master. Any chance of pushing a new release? |
She solved my problem by specifying a commit from main.
Would be highly appreciated. |
I still see that this is unresolved in release, but resolved in latest git. What hinders making a new release, so that distributions can pick up? Regards! |
Sadly, I think it's pretty safe to say this package is no longer maintained. |
I'm trying to add python 3.11 to run the tests for Qtile on github.
A couple of our tests in qtile use the sync methods of dbus_next and these fail under 3.11.
Digging in to this some more, it seems that any
_sync
method triggers this.For example, running the example at https://github.com/altdesktop/python-dbus-next/blob/master/examples/glib-list-names.py triggers the same segfault.
Core Dump (not sure if this helps)
EDIT: I wonder if this is actually a fault in the glib mainloop. Let me test a bit more.
EDIT 2: No. Basic MainLoop examples run ok on python 3.11.
The text was updated successfully, but these errors were encountered: