Fix raw PyTorch clip under non-PyTorch backends#3433
Merged
Conversation
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
49a6ea8 to
4d7f60c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
pyrecest.backend_supportso rawpyrecest._backend.pytorch.clipaccepts NumPy-style array-like inputs even when the active public backend is not PyTorch.a_min/a_max,min/max, andout=handling while updating the active public PyTorch facade when applicable.PYRECEST_BACKEND=numpywith direct raw PyTorchclipaccess.Bug fixed
With the default/NumPy public backend, importing
pyrecestdid not apply the PyTorchclipwrapper because the existing facade patch returns early unlessPYRECEST_BACKEND=pytorch. Direct calls such aspyrecest._backend.pytorch.clip([-2.0, 0.5, 3.0], -1.0, 2.0)therefore reachedtorch.clipwith a Python list and failed before backend conversion.Testing
tests/backend_support/test_pytorch_clip_default_backend.py.torchpackage; full repository tests were not run in this connector session.