What types of changes does your code introduce to quinn?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Further comments
Since keyword_finder.py is new, I think we should replace input as a variable name with something like input_string or original to avoid overshadowing the default input python keyword. I added a file-scoped ruff lint ignore rule (A002) to bypass this for now.
Proposed changes
Fixes ruff lint in recently added/modified files.
Types of changes
What types of changes does your code introduce to quinn? Put an
xin the boxes that applyFurther comments
Since
keyword_finder.pyis new, I think we should replaceinputas a variable name with something likeinput_stringororiginalto avoid overshadowing the defaultinputpython keyword. I added a file-scoped ruff lint ignore rule (A002) to bypass this for now.