Closed ckolbPTB closed 2 months ago
Coverage Report
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
762 | 0 :zzz: | 0 :x: | 0 :fire: | 1m 9s :stopwatch: |
Currently all warnings are raised as errors in pytest (see https://github.com/PTB-MR/mrpro/blob/ca2f07b7030fe8ce3674f23207f974efcbc09fd3/pyproject.toml#L66)
This means that e.g DeprecationWarnings in other packages lead to errors. @fzimmermann89 @schuenke : Is this the behaviour we want, or should it only lead to errors for warning raised directly by our mrpro code?
DeprecationWarnings as errors makes sense IMHO.
It would be better if we could somehow set a depth for this, i.e. only if we call deprecated code it should error, not if one of our dependencies calls a deprecated function. But I think that might not be possible to detect..
(If third party code throws a DeprecationWarning that we cannot fix, we could add an ignore to the toml filter warning setting for this deprecating warning)
@CodiumAI-Agent /review
⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪ |
🧪 No relevant tests |
🔒 No security concerns identified |
⚡ Key issues to review Type Consistency The function `get_item` and `get_items_from_all_dicoms` have changed the type of the `name` parameter from `str | TagType` to `TagType` only. Ensure that this change does not break existing functionality where a string might be passed. |
Got it, TagType includes str
...and you already answered the question :D sorry
Persistent review updated to latest commit https://github.com/PTB-MR/mrpro/commit/c51e21ff4796e14f19aa072ab56022a166fe9775
Persistent review updated to latest commit https://github.com/PTB-MR/mrpro/commit/6bbf37f3170b789183db2e41d140232d9a46afac
Pydicom 3.0 was released which led to several errors due to deprecation, see e.g. https://github.com/pydicom/pydicom/pull/1567/files#diff-9b5a2e48457143cde31b1bbe1c7546a6733e577c306cfe582d56099851e12468