<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - libxcb 1.12 does not build with python 3.4" href="https://bugs.freedesktop.org/show_bug.cgi?id=96395#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - libxcb 1.12 does not build with python 3.4" href="https://bugs.freedesktop.org/show_bug.cgi?id=96395">bug 96395</a> from <a class="email" href="mailto:josh@freedesktop.org" title="Josh Triplett <josh@freedesktop.org>"> Josh Triplett</a> <pre>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 (<a href="https://www.python.org/dev/peps/pep-0394/">https://www.python.org/dev/peps/pep-0394/</a>), 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 lines. Similarly, in configure.ac, after calling AM_PATH_PYTHON, we should check that $PYTHON_VERSION starts with "2.".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>