Support passing np.timedelta64 to parameters that expect a sequence (e.g., 'region')

[seisman]

Related to #2848.

import pygmt
import numpy as np

fig = pygmt.Figure()
fig.basemap(
    projection="X8c/5c",
    region=[np.timedelta64(0, "D"), np.timedelta64(8, "D"), 0, 10],
    frame=["WSne", "xaf+lForecast Days", "yaf+lRMSE"],
)
fig.plot(
    x=np.arange(np.timedelta64(0, "D"), np.timedelta64(8, "D")),
    y=np.geomspace(start=0.1, stop=9, num=8),
    style="c0.2c",
    pen="1p",
)
fig.show()

[Copilot]

Pull request overview

This PR adds support for passing np.timedelta64 objects to parameters that expect a sequence, such as the region parameter in GMT plotting functions. The implementation converts timedelta64 objects to their numeric values in their original units when joining sequences into strings.

Changes:

• Modified sequence_join function in pygmt/helpers/utils.py to handle np.timedelta64 objects by extracting their numeric values
• Updated test_plot_timedelta64 test to use timedelta64 objects in the region parameter, testing the new functionality
• Added comprehensive docstring examples showing timedelta64 handling with various time units

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
pygmt/helpers/utils.py	Added timedelta64 handling logic to convert timedelta64 objects to numeric strings, and updated docstring with examples
pygmt/tests/test_plot.py	Refactored test to use timedelta64 objects in the region parameter, testing the new functionality

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will not alter performance

_{Comparing timedelta64/support (92280b9) with main (3175d52)}

Summary

✅ 104 untouched benchmarks

[weiji14]

Why is item converted into a timedelta64 value again here?

[seisman]

You're right, conversion is not necessary. Simplified in 92280b9.