Closed Marsmaennchen221 closed 2 months ago
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
✅ REPOSITORY | git_diff | yes | no | 0.38s |
See detailed report in MegaLinter reports
_Set VALIDATE_ALL_CODEBASE: true
in mega-linter.yml to validate all sources, not only the diff_
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 97.73%. Comparing base (
254617c
) to head (af4174f
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Why do we need to pin the version of transitive dependencies? Doesn't torchvision declare itself that it needs major version 1 for numpy?
Why do we need to pin the version of transitive dependencies? Doesn't torchvision declare itself that it needs major version 1 for numpy?
torchvision does not specify any restrictions on the numpy version and as of pytorch version 2.3.0 pytorch does support numpy v2.0. While torchvision claims to be 98% compatible to Numpy v2.0, a few important methods like read_image
or save_image
do not support v2.0. So if you install the most recent version of safe-ds you will get numpy 2.0, but a few key methods like Image.from_file
will not work.
torchvision does not specify any restrictions on the numpy version
ðŸ˜
:tada: This PR is included in version 0.27.0 :tada:
The release is available on:
v0.27.0
Your semantic-release bot :package::rocket:
Summary of Changes
Add clause to
pyproject.toml
to use a numpy version below 2.0 as torchvision does not yet support numpy 2.0 (See #898)