Fix utils.signal_index() under pandas>=3.0

[hagenw]

Ensures we use ns time resolution in audinterface.utils.signal_index() and in tests to work under pandas >=3.0.

[sourcery-ai]

Reviewer's Guide

Normalizes time handling to nanosecond resolution in utils.signal_index() and related tests to ensure compatibility with pandas>=3.0, while simplifying several test expectations to rely on existing table structures and centralizing index construction through signal_index().

File-Level Changes

Change	Details	Files
Normalize signal index construction and duration handling to nanosecond Timedelta resolution for pandas>=3.0.	Wrap TimedeltaIndex creation for signal starts and ends with .as_unit('ns') in signal_index(). Ensure pd.Timedelta inputs in duration_in_seconds() are normalized via .as_unit('ns'). Apply .as_unit('ns') to pd.to_timedelta() outputs in duration_in_seconds() to keep consistent nanosecond precision.	audinterface/core/utils.py
Update tests to expect nanosecond-resolution timedelta indexes and to reuse existing table dataframes instead of reconstructing them manually.	Replace manually constructed DataFrame expectations with copies of table_df.get() whose index is overridden with the expected MultiIndex. Adjust read_audio tests to construct expected MultiIndex levels using TimedeltaIndex(...).as_unit('ns') to match new nanosecond resolution. Refactor segment-with-feature tests to build indexes via audinterface.utils.signal_index() instead of pd.MultiIndex.from_tuples(). Update process() helper in tests to compute duration with audinterface.utils.to_timedelta() and reuse that when calling signal_index().	tests/test_segment.py tests/test_utils.py tests/test_segment_with_feature.py tests/test_process.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (72d48c8) to head (76059cd).

Additional details and impacted files

Files with missing lines	Coverage Δ
audinterface/core/utils.py	100.0% <100.0%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.