Refactor PyNEST example: Potjans_2014/helpers.py #3348
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.
Pylint Static Code Analysis reports the following code quality issue:
Potjans_2014/helpers.py:142:0: R0917: Too many positional arguments (11/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.
The text was updated successfully, but these errors were encountered: