Summary: | xpyb: damage.py does not work: "NameError: global name 'RECTANGLE' is not defined" | ||
---|---|---|---|
Product: | XCB | Reporter: | Dan McDougall <daniel.mcdougall> |
Component: | Library | Assignee: | xcb mailing list dummy <xcb> |
Status: | RESOLVED MOVED | QA Contact: | xcb mailing list dummy <xcb> |
Severity: | major | ||
Priority: | medium | ||
Version: | 1.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Output from make
config.log Patch to fix RECTANGLE namespace. |
Description
Dan McDougall
2013-02-08 16:04:35 UTC
Could you attach the config.log and output of make, please? (I can't reproduce this on ArchLinux with Python 2.7. With Python 3.3 configure fires an "invalid syntax" error when searching for the include path. But, that should be a different bug.) Created attachment 74702 [details]
Output from make
Created attachment 74703 [details]
config.log
The make output as well as the config.log are attached. I ran into the same problem on Debian unstable using python-xcbgen 1.10-1. I don't have convenient access to an Arch system, but it's hard for me to understand how it could be working. Is damage.py on Arch ending up with references to xproto.RECTANGLE? Or is RECTANGLE somehow getting loaded by damage.py? From my brief scan, it looked to me like the problem is that py_client.py:_t is stripping the namespace information from types before emitting. I was able to fix the problem for my purposes with the attached patch. I undoubtedly missed some cases. I'm happy to clean it up for submission if it turns out I am on the right track. Created attachment 105182 [details] [review] Patch to fix RECTANGLE namespace. -- 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/6. |
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.