ci/pylama: Added pylama config file
Checks
| Context |
Check |
Description |
| ci/Intel-dts-suite-test |
warning
|
SKIPPED
|
Commit Message
From: Owen Hilyard <ohilyard@iol.unh.edu>
I ended up turning off most of the formatting-releated checks due to
some minor conflicts with black (black allows lines > 80 characters for
instance). This produces a very substantial list of errors, some of
which may need to be simply disabled instead of being fixed due to
architectural reasons.
Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
---
ci/requirements.txt | 5 ++++-
pylama.ini | 5 +++++
2 files changed, 9 insertions(+), 1 deletion(-)
create mode 100644 pylama.ini
Comments
This depends on the requirements file that I added when adding the other ci
script. I want to make it as easy as possible to install everything needed
for CI, which means all of it should go in one requirements file. Even with
my removing many issues, this still has a lot of issues with the DTS
codebase, 35126 issues to be exact. We may want to bring this back to the
working group and discuss more, after fixing just the errors, since there
is a manageable amount of those.
On Thu, Aug 12, 2021 at 12:23 PM <ohilyard@iol.unh.edu> wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> I ended up turning off most of the formatting-releated checks due to
> some minor conflicts with black (black allows lines > 80 characters for
> instance). This produces a very substantial list of errors, some of
> which may need to be simply disabled instead of being fixed due to
> architectural reasons.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
> ci/requirements.txt | 5 ++++-
> pylama.ini | 5 +++++
> 2 files changed, 9 insertions(+), 1 deletion(-)
> create mode 100644 pylama.ini
>
> diff --git a/ci/requirements.txt b/ci/requirements.txt
> index 0abd6716..e19e540e 100644
> --- a/ci/requirements.txt
> +++ b/ci/requirements.txt
> @@ -29,4 +29,7 @@
> # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> -argparse==1.4.0
> \ No newline at end of file
> +argparse==1.4.0
> +pylama
> +pylama_pylint
> +black
> \ No newline at end of file
> diff --git a/pylama.ini b/pylama.ini
> new file mode 100644
> index 00000000..aef408c0
> --- /dev/null
> +++ b/pylama.ini
> @@ -0,0 +1,5 @@
> +[pylama]
> +format = pylint
> +linters = pep8,pycodestyle,pylint
> +ignore = F0401,C0111,E731,E266,E501,E203
> +
> --
> 2.30.2
>
>
> -----Original Message-----
> From: ohilyard@iol.unh.edu <ohilyard@iol.unh.edu>
> Sent: 2021年8月13日 0:23
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>; juraj.linkes@pantheon.tech; Owen Hilyard
> <ohilyard@iol.unh.edu>
> Subject: [PATCH] ci/pylama: Added pylama config file
>
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> I ended up turning off most of the formatting-releated checks due to some
> minor conflicts with black (black allows lines > 80 characters for instance). This
> produces a very substantial list of errors, some of which may need to be simply
> disabled instead of being fixed due to architectural reasons.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
Applied
@@ -29,4 +29,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-argparse==1.4.0
\ No newline at end of file
+argparse==1.4.0
+pylama
+pylama_pylint
+black
\ No newline at end of file
new file mode 100644
@@ -0,0 +1,5 @@
+[pylama]
+format = pylint
+linters = pep8,pycodestyle,pylint
+ignore = F0401,C0111,E731,E266,E501,E203
+