From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: devel@edk2.groups.io, joeyvagedes@microsoft.com,
Rebecca Cran <rebecca@bsdio.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Sean <spbrogan@outlook.com>,
Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] Fixing edk2-basetools CI
Date: Mon, 12 Feb 2024 09:42:18 -0700 [thread overview]
Message-ID: <2c52fbac-dbe1-423a-a9d7-0bbe473cd9e9@os.amperecomputing.com> (raw)
In-Reply-To: <BY1PR21MB394351987956233AFF2CFB3DBF482@BY1PR21MB3943.namprd21.prod.outlook.com>
On 2/12/2024 9:08 AM, Joey Vagedes via groups.io wrote:
> Hello. It can be simplified - You can view the pyproject.toml for edk2-pytool-library and edk2-pytool-extensions:
>
> https://github.com/tianocore/edk2-pytool-library/blob/master/pyproject.toml
>
> Also, Why disable flake8 rather than fix the changes? I also suggest switching to ruff, as it does the same thing but better, and with way more rules / configuration options.
Thanks. I'm not sure that looks so much simpler than my pyproject.toml
but I'll update it to follow the same layout. Also, pyproject.toml says
it's using the setuptools build backend but you don't have a setup.py:
how does that work?
I decided to disable flake8 for now because the BaseTools Python code is
very non-compliant: the log file has over 41,000 lines. In most places
it looks like people have been trying to write it as C code.
A few of the lines:
.\edk2basetools\Common\TargetTxtClassObject.py:44:80: E203 whitespace
before ':'
.\edk2basetools\Common\TargetTxtClassObject.py:61:14: E111 indentation
is not a multiple of 4
.\edk2basetools\Common\TargetTxtClassObject.py:61:14: E117 over-indented
.\edk2basetools\Common\TargetTxtClassObject.py:63:50: F405
'FILE_NOT_FOUND' may be undefined, or defined from star imports:
.BuildToolError
.\edk2basetools\Common\TargetTxtClassObject.py:73:121: E501 line too
long (123 > 120 characters)
.\edk2basetools\Common\TargetTxtClassObject.py:84:38: F405
'FILE_OPEN_FAILURE' may be undefined, or defined from star imports:
.BuildToolError
.\edk2basetools\Common\TargetTxtClassObject.py:100:108: E502 the
backslash is redundant between brackets
.\edk2basetools\Common\TargetTxtClassObject.py:108:121: E501 line too
long (139 > 120 characters)
.\edk2basetools\Common\TargetTxtClassObject.py:118:121: E501 line too
long (140 > 120 characters)
.\edk2basetools\Common\TargetTxtClassObject.py:123:97: E502 the
backslash is redundant between brackets
.\edk2basetools\Common\TargetTxtClassObject.py:128:21: F841 local
variable 'V' is assigned to but never used
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115360): https://edk2.groups.io/g/devel/message/115360
Mute This Topic: https://groups.io/mt/104306226/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-12 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 4:14 [edk2-devel] Fixing edk2-basetools CI Rebecca Cran
2024-02-12 6:03 ` Michael D Kinney
2024-02-12 11:26 ` Rebecca Cran
2024-02-12 16:08 ` Joey Vagedes via groups.io
2024-02-12 16:42 ` Rebecca Cran via groups.io [this message]
2024-02-12 17:06 ` Joey Vagedes via groups.io
2024-02-13 19:27 ` Rebecca Cran
2024-02-13 19:42 ` Joey Vagedes via groups.io
2024-02-13 19:46 ` Rebecca Cran
2024-02-16 7:51 ` Rebecca Cran
2024-02-16 17:24 ` Michael D Kinney
2024-02-23 7:55 ` Yuwei Chen
2024-02-23 14:48 ` Rebecca Cran
[not found] ` <17B6855E281DBF07.24621@groups.io>
2024-02-23 22:40 ` Rebecca Cran
2024-02-27 1:49 ` Rebecca Cran
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-list 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=2c52fbac-dbe1-423a-a9d7-0bbe473cd9e9@os.amperecomputing.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox