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
In GMT, coast is called a "module", which makes sense because GMT is a CLI program. In PyGMT, sometimes we say "the coast method", but sometimes we also say "the coast module" (for example, https://www.pygmt.org/dev/get-started/first_figure.html).
In the Python world, a module usually means a Python file with some functions, and one can import the functions in the module using from xxmodule import yyfunc, but that's not the case for a PyGMT "module". I'm afraid it may cause some confusion for non-GMT users.
Should we not say "the coast module", and consitenly say "the coast method" instead?
The text was updated successfully, but these errors were encountered:
In GMT,
coast
is called a "module", which makes sense because GMT is a CLI program. In PyGMT, sometimes we say "the coast method", but sometimes we also say "the coast module" (for example, https://www.pygmt.org/dev/get-started/first_figure.html).In the Python world, a
module
usually means a Python file with some functions, and one can import the functions in the module usingfrom xxmodule import yyfunc
, but that's not the case for a PyGMT "module". I'm afraid it may cause some confusion for non-GMT users.Should we not say "the coast module", and consitenly say "the coast method" instead?
The text was updated successfully, but these errors were encountered: