Used some flake8 rules to clean up the code a bit more

[marksmayo]

Used flake8 to identify some issues

Style and cleanliness change

• [X ] Bug fix (non-breaking change which fixes an issue)

Checklist:

• [X ] My code follows the style guidelines of this project
• [ X] I have performed a self-review of my own code
• [X ] I have commented my code, particularly in hard-to-understand areas
• [X ] I have made corresponding changes to the documentation
• [X ] My changes generate no new warnings
• [X ] I have added tests that prove my fix is effective or that my feature works
• [NA ] New and existing unit tests pass locally with my changes (not just the CI)
• [NA ] Any dependent changes have been merged and published in downstream modules
• [NA ] I have labeled my PR using appropriate tags (in particular using status labels like Status: Code Review Needed, Business: Test Needed or Status: In Progress if you are still working on the PR)

Do not forget to @ the people that needs to do the review

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[marksmayo]

It looks like when I pulled, I got a new setup.py and it's having issues install?

[js-dieu]

Hello! Thanks for reaching out!
I started some clean up and alignment with new python standards. As setuptools is being deprecated, the pyproject.toml is the new de facto way of doing.
Have you tried the following (run it under pytest-monitor root folder)

For development purpose:
python -m pip install -e .

For simple install:
python -m pip install .