-
Notifications
You must be signed in to change notification settings - Fork 219
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.
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
Parameters vs Arguments? #886
Comments
A quick CTRL+F yielded >100 instances of 'argument' in the PyGMT project currently. Some are correctly called 'argument', but not all of them. It will be a big task to replace all of them, so maybe just be careful going forward and replace things on an ad-hoc basis (e.g. when refactoring stuff). I think most people won't get too hung up on whether we call it 'parameter' or 'argument', they know that it is 'something' handled by the program. As for 'option', I think it's fine to use as a synonym for 'parameter'. |
Yes, I agree. It would be better to document it in the contributing guides. |
In #881, I found that another common inconsistency involved referencing the arguments of parameters as options. Based on this discussion, it seems that these should be only referred to as 'arguments' if 'option' is a synonym for 'parameter'. |
Almost done. Closing the issue. |
For function parameters like
frame
,region
, we're inconsistently calling them "parameters", "arguments", or "options".I thought the correct way is calling
frame
an "argument", but after reading this FAQ (https://docs.python.org/3.9/faq/programming.html#faq-argument-vs-parameter), I think we should callframe
a "parameter".Thoughts? @GenericMappingTools/python @GenericMappingTools/python-maintainers
The text was updated successfully, but these errors were encountered: