You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new pylint check is going to bite us in Pylint 3.3 (2024-09-20): by default, pylint now complains about functions that have more then five (positional) arguments (pylint-dev/pylint#9099). That is, it warns when it encounters a function like def f(a=1, b=2, c=3, d=4, e=5, f=6).
I suggest globally disabling this check in Orange and related projects.
There was a dissenting opinion that there is "no obvious refactoring path for reasonable number of positional-only arguments" (unfortunately the comment was too late to be taken into consideration).
I don't think this is something we need to worry about in our code base. Our functions with many arguments usually have default values and we use named arguments in function calls, so these arguments are effectively keyword-only, although not marked as such.
We relatively rarely specify arguments as keywords-only (by putting a * in the argument list), so fixing this could take us a person-week -- and it wouldn't be time well-spent.
The text was updated successfully, but these errors were encountered:
A new pylint check is going to bite us in Pylint 3.3 (2024-09-20): by default, pylint now complains about functions that have more then five (positional) arguments (pylint-dev/pylint#9099). That is, it warns when it encounters a function like
def f(a=1, b=2, c=3, d=4, e=5, f=6)
.I suggest globally disabling this check in Orange and related projects.
*
in the argument list), so fixing this could take us a person-week -- and it wouldn't be time well-spent.The text was updated successfully, but these errors were encountered: