The proposal to merge lp:~dmitrij.ledkov/apparmor/py3 into lp:apparmor has been updated.
Description changed to: This is a complete port to make apparmor Python2/Python3 bilingual. There are 3 variables in use: PYTHON, used by common/Make.rule and libapparmor configure script pointing to a python interpreter PYTHON_VERSION, used by libapparmor configure script with just version number e.g. '3.2' or '2.7' PYTHON_VERSIONS, list of all pythons to run checks/tests with for python utilities e.g. 'python2 python3' If none are specified, defaults will be autodetected to: PYTHON=/usr/bin/python2 in Make.rule PYTHON=/usr/bin/python2.7 in configure PYTHON_VERSION=2.7 PYTHON_VERSIONS='python2 python3' To build libapparmor (including the python swig bindings) with python3 it seems like you must set these two variables: PYTHON=/usr/bin/python3.2 PYTHON_VERSIONS=3.2 All test and check targets pass and build succeeds. Scripts are functional. Swig python module can import and doesn't segfault in smoke testing. TODO: /usr/bin/aa-easyprof gets installed without updated shebang to point at python3 ac_python_devel patch should probably be submitted to autoconf-archive (updating it's ax_python_devel), not sure about the install location as historically a*_python_devel installs into site-packages, instead of dist-packages. For more details, see: https://code.launchpad.net/~dmitrij.ledkov/apparmor/py3/+merge/109682 -- https://code.launchpad.net/~dmitrij.ledkov/apparmor/py3/+merge/109682 Your team AppArmor Developers is requested to review the proposed merge of lp:~dmitrij.ledkov/apparmor/py3 into lp:apparmor. -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
