replace AutoFeatureExtractor with AutoImageProcessor in docs#8200
Open
ajaystar8 wants to merge 1 commit into
Open
replace AutoFeatureExtractor with AutoImageProcessor in docs#8200ajaystar8 wants to merge 1 commit into
ajaystar8 wants to merge 1 commit into
Conversation
vitoriall
reviewed
May 21, 2026
|
|
||
| ```py | ||
| >>> from transformers import AutoFeatureExtractor | ||
| >>> from transformers import AutoImageProcessor |
There was a problem hiding this comment.
Good update! This aligns with the AutoImageProcessor migration
in the transformers library. The variable rename from
feature_extractor to image_processor also improves clarity.
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
2 participants
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.
Closes #8199
What does this PR do?
Replaces
AutoFeatureExtractorwithAutoImageProcessorin the image augmentation example indocs/source/use_dataset.mdx. For vision models,AutoImageProcessoris the recommended API and better reflects currenttransformersconventions.This is consistent with the direction taken in the
transformerslibrary itself — see PR #20111 and PR #20501, where vision feature extractor references were systematically replaced with image processors across thetransformerscodebase and documentation. Thedatasetsdocs were not in scope for that PR, making this a natural follow-up.