Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor PyNEST example: eprop_supervised_classification_evidence-accumulation.py #3351

Open
gtrensch opened this issue Oct 22, 2024 · 0 comments
Open

Refactor PyNEST example: eprop_supervised_classification_evidence-accumulation.py #3351

gtrensch opened this issue Oct 22, 2024 · 0 comments
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.

Comments

@gtrensch
Copy link
Contributor

Pylint Static Code Analysis reports the following code quality issues:

eprop_supervised_classification_evidence-accumulation.py:436:0: R0917: Too many positional arguments (7/5)
eprop_supervised_classification_evidence-accumulation.py:716:0: R0917: Too many positional arguments (6/5)

This was causing builds to fail. Currently, we have lowered the fail-threshold for pylint (#3339) to allow merges to continue. The PyNEST example needs to be refactored to achieve the desired code quality.
@jessica-mitchell jessica-mitchell added S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Oct 28, 2024
@github-project-automation github-project-automation bot moved this to To do in PyNEST Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.
Projects
PyNEST
Status: To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jessica-mitchell @gtrensch