remove custom types defintions from datapoints module #7814
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.
This does two things:
_FillType
and_FillTypeJIT
fromtorchvision.datapoints
totorchvision.transforms.v2.functional
. We only had them in the datapoints module before, since we needed them to annotate the methods on the classes due to our convoluted dispatch mechanism. With the new one in place, there is no need to keep it there anymore._InputType
,_InputTypeJIT
, ..., types, since they added very little value. After move passthrough for unknown types from dispatchers to transforms #7804, they will also be wrong, since we let_transform
handle the unsupported types automatically, rather than hardcoding it.cc @vfdev-5