Add uppercased versions of image file extensions for automatic module inference #4515
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.
Adds the uppercased versions of the image file extensions to the supported extensions.
Another approach would be to call
.lower()on extensions while resolving data files, but uppercased extensions are not something we want to encourage out of the box IMO unless they are commonly used (as they are in the vision domain)Note that there is a slight discrepancy between the image file resolution and
imagefolderas the latter calls.lower()on file extensions leading to some image file extensions being ignored by the resolution but not by the loader (e.g.pNg). Such extensions should also be discouraged, so I'm ignoring that case too.Fix #4514.