Remove deprecated max_size parameter from ConditionalDetr image processors #40299
+23
−3,086
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
This PR removes the deprecated
max_size
parameter from bothConditionalDetrImageProcessor
andConditionalDetrImageProcessorFast
classes.Fixes
Closes #37939
Changes
max_size
parameter handling fromConditionalDetrImageProcessor.__init__
max_size
parameter handling fromConditionalDetrImageProcessorFast.__init__
max_size
parameter handling fromfrom_dict
methods in both classesmax_size
parameter handling frompreprocess
/resize
methodsBreaking Change
max_size
parameter is no longer accepted.Users should migrate to using
size['longest_edge']
instead:Justification
The
max_size
parameter was marked for deprecation and scheduled for removal in v4.26. The current version is v4.56, so this removal is long overdue. The deprecation warnings have been showing for many versions, giving users ample time to migrate their code.Testing
max_size
parameter is no longer accepted and raisesTypeError
size
parameter still works correctly