Post capgen unification: pylint code
Open
Nobody has claimed this yet.
enhancement
post-capgen-unification
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
As of 2024-03-08:
> cd test
> ./pylint_test.sh
...
------------------------------------------------------------------
Your code has been rated at 8.48/10 (previous run: 8.48/10, +0.00)
This is likely going to change while we transition from prebuild to capgen and add, remove, modify features.
Solution
Fix coding style after capgen unification
Alternatives (optional)
Leave as is - not a good idea
Related to (optional)
n/a
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running test/pylint_test.sh to inspect the current pylint output and identify the style violations introduced or exposed by capgen unification. Review the affected Python code and project conventions, then confirm the check passes with the intended improved rating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100