Am Dienstag, 20. September 2016, 11:51:47 CEST schrieb Steve Beattie:
> On Tue, Sep 20, 2016 at 11:45:23AM -0700, Steve Beattie wrote:
> > Once we kill python2.7 support, then we can go with the "simple"
> > form of the __init__.py file.
> Which reminds me, we ought to note that we're going to kill python 2.7
> support in the README file. I moved the required versions section
> nearer to the beginning and dropped the bit about aa-exec depending
> on perl, since it's now a compiled binary.

I already have a patch for that ;-)
    [patch] Switch utils to python3

Besides switching all tools and tests to py3, this patch includes a
README update:

=== modified file ./'README'
--- README  2016-01-27 21:47:09 +0000
+++ README  2016-08-23 17:24:29 +0000
@@ -232,7 +232,8 @@
 installed and available versions of other tools. This is a (possibly
 incomplete) list of known version dependencies:
-The Python utilities require a minimum of Python 2.7 or Python 3.3.
+The Python utilities require a minimum of Python 2.7 (deprecated) or Python 
+Python 3.x is recommended. Python 2.x support is deprecated since AppArmor 
 Some utilities (aa-exec, aa-notify and aa-decode) require Perl 5.10.1 or newer.

This patch was already acked by Seth, but it depends on the FileRule 
series (it changes test-file.py), so I'll have to wait with commiting 
it until someone finishes the review of the FileRule series.

So the question is - your patch or mine? ;-)

Note that my patch doesn't drop the perl dependency notice for aa-exec,
so if we go for my patch, we'll still need to change this.


Christian Boltz
aus meiner Sicht ist [der Verfassungsschutz] jedenfalls unfähig, auch
nur einen gebrauchten Pappteller ohne Spätschäden für die zivilisierte
Gesellschaft zu bewachen.

Attachment: signature.asc
Description: This is a digitally signed message part.

AppArmor mailing list
Modify settings or unsubscribe at: 

Reply via email to