From: "Paul Barker" <pbarker@konsulko.com>
To: Persian Prince <persianpros@yahoo.com>
Cc: Armin Kuster <akuster808@gmail.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/8] Safe PEP8
Date: Tue, 29 Jun 2021 17:32:33 +0100 [thread overview]
Message-ID: <CAM9ZRVsNs-vxRFqxn3KvPCgBzYMheDCMwsG_w4ebELnnv_be1Q@mail.gmail.com> (raw)
In-Reply-To: <1684669268.2868693.1624983560306@mail.yahoo.com>
On Tue, 29 Jun 2021 at 17:19, Persian Prince <persianpros@yahoo.com> wrote:
>
> @Paul Barker
>
> I spent days and nights for testing the outcome of my PEP8.sh script and I used it on more than 100 repos to check the results, what you see now is the result of that.
>
> People at https://github.com/OpenVisionE2 , https://github.com/OpenPLi , https://github.com/oe-alliance and more other teams like ViX, ATV and ... trusted my work and all those are using the changed codes for months!
>
> This is why I write "Safe PEP8" not just "PEP8" as if you just run a normal PEP8 on your repos you'll end up with dead ones.
>
> If you check https://github.com/openembedded/meta-openembedded you're using my changes for 3 months on this repo also so I don't get you being rude.
Please start with
https://docs.yoctoproject.org/dev-manual/common-tasks.html#making-changes-to-the-yocto-project
which documents the way to make contributions to the project. If
you're using an automated tool please give a quick description of it
alongside the changes, preferably with a link to its source code.
You may also want to check
https://git.openembedded.org/openembedded-core/tree/scripts/oe-pylint.
Running that script should flag up errors which we do want to see
fixed. If there are more warnings & errors to consider then these
should be added to that script or to a pylint/pep8/flake8 config file
so that we can run this against all new patches in the future.
--
Paul Barker
Konsulko Group
prev parent reply other threads:[~2021-06-29 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 14:08 [PATCH 0/8] Safe PEP8 Armin Kuster
2021-06-29 14:08 ` [PATCH 1/8] PEP8 double aggressive E401 Armin Kuster
2021-06-29 14:08 ` [PATCH 2/8] PEP8 double aggressive E701, E70 and E502 Armin Kuster
2021-06-29 14:08 ` [PATCH 3/8] PEP8 double aggressive E251 and E252 Armin Kuster
2021-06-29 14:08 ` [PATCH 4/8] PEP8 double aggressive E20 and E211 Armin Kuster
2021-06-29 14:08 ` [PATCH 5/8] PEP8 double aggressive E22, E224, E241, E242 and E27 Armin Kuster
2021-06-29 14:08 ` [PATCH 6/8] PEP8 double aggressive E225 ~ E228 and E231 Armin Kuster
2021-06-29 14:08 ` [PATCH 7/8] PEP8 double aggressive E301 ~ E306 Armin Kuster
2021-06-29 14:08 ` [PATCH 8/8] PEP8 double aggressive W291 ~ W293 and W391 Armin Kuster
2021-06-29 15:54 ` [OE-core] [PATCH 0/8] Safe PEP8 Paul Barker
[not found] ` <1684669268.2868693.1624983560306@mail.yahoo.com>
2021-06-29 16:32 ` Paul Barker [this message]
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=CAM9ZRVsNs-vxRFqxn3KvPCgBzYMheDCMwsG_w4ebELnnv_be1Q@mail.gmail.com \
--to=pbarker@konsulko.com \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=persianpros@yahoo.com \
/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.