| Summary: | Python3 bindings for XCB | ||
|---|---|---|---|
| Product: | XCB | Reporter: | amit.prakash.ambasta |
| Component: | Library | Assignee: | xcb mailing list dummy <xcb> |
| Status: | RESOLVED MOVED | QA Contact: | xcb mailing list dummy <xcb> |
| Severity: | enhancement | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
amit.prakash.ambasta
2014-12-06 11:26:09 UTC
I started porting xpyb to Python 3 for some work I have been doing. It's working, but the patch still needs a lot of work. The biggest outstanding problem is that I need to go through and fix up the buffer ownership issues for both Python 2 and Python 3. The current patch leaks reply data .... and I think the original code leaks event data as well. It's hard to tell for sure since the XCB documentation isn't overly explicit about who owns what returned memory buffers. I'll try to clean up the patch, but am pointing you to it as a reference in case it's useful. https://github.com/Hadron/xpyb -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxcb/issues/33. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.