Figure.plot: Add alias "fill_between" for option -M

[yvonnefroehlich]

Description of proposed changes

This PR aims to add an alias for M of plot (new in GMT 6.5.0).
Sofar I use fillcurves. But @GenericMappingTools/gmt-maintainers feel free to make suggestions for another / a better alias 🙂. Edit: changed to fill_between.

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash command is:

• /format: automatically format and lint the code

[yvonnefroehlich]

/format

[yvonnefroehlich]

/format

[seisman]

This reminds me the fill_between method in matplotlib, so another high-level method for Figure.plot. I guess we need to focus on #2797 in PyGMT v0.13.0.

[yvonnefroehlich]

This reminds me the fill_between method in matplotlib, so another high-level method for Figure.plot. I guess we need to focus on #2797 in PyGMT v0.13.0.

You are probably right, and a high-level method would be more user-friendly and more Pythonic. Despite this, should I still continue working on adding an alias for M or should we close this PR and the PR for the related gallery example?

[seisman]

This reminds me the fill_between method in matplotlib, so another high-level method for Figure.plot. I guess we need to focus on #2797 in PyGMT v0.13.0.

You are probably right, and a high-level method would be more user-friendly and more Pythonic. Despite this, should I still continue working on adding an alias for M or should we close this PR and the PR for the related gallery example?

Personally I prefer to have v0.12.0 released soon and then focus on improving Figure.plot/Figure.plot3d and implementing the proposed high-level wrappers (#2797) in v0.13.0. With the new wrappers, the gallery examples you're working on can be greatly simplified.

[yvonnefroehlich]

This reminds me the fill_between method in matplotlib, so another high-level method for Figure.plot. I guess we need to focus on #2797 in PyGMT v0.13.0.

You are probably right, and a high-level method would be more user-friendly and more Pythonic. Despite this, should I still continue working on adding an alias for M or should we close this PR and the PR for the related gallery example?

Personally I prefer to have v0.12.0 released soon and then focus on improving Figure.plot/Figure.plot3d and implementing the proposed high-level wrappers (#2797) in v0.13.0. With the new wrappers, the gallery examples you're working on can be greatly simplified.

I agree that we should focus to get v0.12.0 out soon (even if I can not state how much I can help out in the next time).
I converted the PRs for the "stem plot" (#3052) and "filled curves" (#3168) gallery examples to drafts.

[yvonnefroehlich]

I am sorry, but it should be between_fill to be consistent with the renaming and the other parameter names.

[seisman]

Actually, I think it should be fill_between, which is more consistent with matplotlib's fill_between method (https://matplotlib.org/stable/api/_as_gen/matplotlib.pyplot.fill_between.html)

[yvonnefroehlich]

Hmm. For Figure.wiggle, we have positive_fill and negative_fill.

What do the others think here @GenericMappingTools/pygmt-maintainers?

[yvonnefroehlich]

Continued in PR #4527.