[Xcb] [Bug 96395] libxcb 1.12 does not build with python 3.4

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jun 5 20:06:22 UTC 2016


--- Comment #1 from Josh Triplett <josh at freedesktop.org> ---
It's clear from the line in the traceback that that's a print statement, not a
print function.  For compatibility, XCB would need to use "from __future__
import print_function" and then switch to using print as a function.

I'm all for making xcbgen work with Python 3, but for the moment, until that
works, could we explicitly use Python 2 to prevent this breakage?

The scripts use "/usr/bin/env python".  "python" should not refer to Python 3,
per PEP 394 (https://www.python.org/dev/peps/pep-0394/), which says "for the
time being, all distributions should ensure that python refers to the same
target as python2"; however, some distributions (including Arch, and apparently
including macports in some configurations) go against that recommendation and
knowingly cause breakage.  To avoid that, we could use "python2" in the shebang

Similarly, in configure.ac, after calling AM_PATH_PYTHON, we should check that
$PYTHON_VERSION starts with "2.".

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/xcb/attachments/20160605/bfdef6d0/attachment.html>

More information about the Xcb mailing list