Open gtdang opened 1 month ago
Hmm, this is curious. I'm guessing the root cause of the emergent flake8 errors is actually due to updates in flake8 or Python itself. We (maybe just me?) used to run flake8 tests locally from the hnn-core/hnn_core
directory before finally installing the VSCode plugin, and none of these errors popped up then. Regardless, thanks for digging into this @gtdang!
Thanks for digging @gtdang ... I agree with @rythorpe that it seems flake8
may have added new rules. Can you check if other repos are following these new rules? E.g., mne-python, numpy, sklearn ... we could add some of the more pedantic rules in the ignores list, specially if they make the code less readable
Fixed any flake8 warning/errors in the codebase. These errors are likely legacy errors that were in the codebase before flake8 gh action checks were fully implemented.
Collaborators can encounter flake8 warnings/errors if they submit a PR in which legacy errors exist in the file they edited. These errors may not be relevant to their PRs.