The xcb-proto package was modified to support being built for multiple Python implementations. However, it installs xcb-proto.pc that has:
even though I hadn't enabled py3.3 on the package. To be honest, I don't see a proper way to support multiple impls with this, so I suggest switching it back to python-single-r1.
Oh, the py3.3 parts are installed as part of multilib, that half of the bug would be my fault.
If you were wondering, libxcb's c_client.py inserts those paths to sys.path which sucks real much. Alternatively, I think we could try to hack it not to do so since it's completely unnecessary. Or convince upstream.
[master 39beabb] x11-proto/xcb-proto: Null out the pythondir in xcb-proto.pc to make xcb-proto useful for any Python implementation.
1 file changed, 3 insertions(+)
I've worked around it in ::x11.
This was fixed in 1.10
The bug has been referenced in the following commit(s):
Author: Matt Turner <firstname.lastname@example.org>
AuthorDate: 2020-02-22 20:28:13 +0000
Commit: Matt Turner <email@example.com>
CommitDate: 2020-02-22 21:06:01 +0000
x11-base/xcb-proto: Version bump to 1.14
Signed-off-by: Matt Turner <firstname.lastname@example.org>
x11-base/xcb-proto/Manifest | 1 +
x11-base/xcb-proto/xcb-proto-1.14.ebuild | 42 ++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+)