From: Stephen Smalley <sds@tycho.nsa.gov>
To: Jason Zaman <jason@perfinion.com>, Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: [GIT PULL] policycoreutils: fix PEP8 issues
Date: Fri, 24 Jul 2015 09:09:54 -0400 [thread overview]
Message-ID: <55B23922.906@tycho.nsa.gov> (raw)
In-Reply-To: <20150724083548.GA11791@meriadoc.perfinion.com>
On 07/24/2015 04:35 AM, Jason Zaman wrote:
> On Fri, Jul 24, 2015 at 04:13:44PM +0800, Jason Zaman wrote:
>> On Fri, Jul 24, 2015 at 09:43:42AM +0200, Petr Lautrbach wrote:
>>> It seems that there's only seobject.py which needs to be ported to
>>> python 3. I would start with the indent conversion as it's needed anyway
>>> and then we could provide a patch with python 3 support based on this
>>> conversion.
>>
>> The following changes since commit d19cda0c80524b57464b3bb74dce1297d017b4b1:
>>
>> Updated libsepol ChangeLog (2015-07-22 11:02:32 -0400)
>>
>> are available in the git repository at:
>>
>> https://github.com/perfinion/selinux.git reformat
>>
>> for you to fetch changes up to 789d0ebbf9fa448b09917ccd0adff91d72e9f5c1:
>>
>> policycoreutils: Fix PEP8 issues (2015-07-24 16:07:13 +0800)
>>
>> ----------------------------------------------------------------
>> Jason Zaman (1):
>> policycoreutils: Fix PEP8 issues
>>
>>
>> I re-did the changes on top of the current master and updated that
>> branch. this is the new commit to pull.
>>
>> All the files now follow PEP8 style (ie tabs are 4 spaces) so future
>> commits should follow that too.
>
> After seobject.py is converted, I see a few issues with
> policycoreutils/sepolicy/sepolicy/*.
>
> The easy stuff 2to3 handles, but it looks like there will need to be
> some changes to the C module, I've got it building by adding some
> #defines for PyInt_AsLong and the like. I am not that familiar with the
> C-Python stuff so it might not be done the right way.
On this, we would prefer to see policycoreutils/sepolicy converted to
use setools4, which directly provides python interfaces, no C extension
required. setools3 is no longer maintained.
next prev parent reply other threads:[~2015-07-24 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 14:28 [GIT PULL] policycoreutils: fix PEP8 issues Jason Zaman
2015-07-22 13:15 ` Stephen Smalley
2015-07-22 14:31 ` Jason Zaman
2015-07-22 14:38 ` Stephen Smalley
2015-07-23 7:14 ` Petr Lautrbach
2015-07-24 7:43 ` Petr Lautrbach
2015-07-24 8:13 ` Jason Zaman
2015-07-24 8:35 ` Jason Zaman
2015-07-24 13:09 ` Stephen Smalley [this message]
2015-07-24 13:06 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B23922.906@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=jason@perfinion.com \
--cc=plautrba@redhat.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.