Do not ignore PytestRemovedIn8Warning.

[hugobuddel]

The main point of treating warnings as errors in the tests is to detect deprecation warningns early, so we have time to fix them before they become errors.

We should only ignore deprecation warnings in very specific cases where we have ensured that doing so is save and will not cause problems.

At the very least, every ignored deprecation warning should come with an issue that describes what is required to fix the problem.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.83%. Comparing base (68832ab) to head (35e9a05).
Report is 81 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #420   +/-   ##
=======================================
  Coverage   74.83%   74.83%           
=======================================
  Files          56       56           
  Lines        7824     7824           
=======================================
  Hits         5855     5855           
  Misses       1969     1969           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[teutoburg]

Let's see what happens then...

[hugobuddel]

I'll let the notebook test here finish to see whether that causes any warnings.

I had never seen that PytestRemovedIn8Warning, so I don't know what should trigger it. Do you recall?

[hugobuddel]

FWIW, PytestRemovedIn8Warning itself is removed in a later version of pytest, so the test I created to use the latest version of all dependencies, AstarVienna/ScopeSim_Data#16, failed: https://github.com/AstarVienna/ScopeSim_Data/actions/runs/9220738690/job/25368339300#step:5:1052

[teutoburg]

Do you recall?

Can't remember. There must have been a good reason once, but that could very well be outdated...