Skip to content

Conversation

@mariosasko
Copy link
Collaborator

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 imagefolder as 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.

@HuggingFaceDocBuilderDev
Copy link

HuggingFaceDocBuilderDev commented Jun 16, 2022

The documentation is not available anymore as the PR was closed or merged.

Copy link
Member

@lhoestq lhoestq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good !

@mariosasko mariosasko merged commit 7cff5b9 into master Jun 16, 2022
@mariosasko mariosasko deleted the fix-4514 branch June 16, 2022 17:11
khushmeeet pushed a commit to khushmeeet/datasets that referenced this pull request Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow .JPEG as a file extension

4 participants