Updated typing for RandomErasing

[ancestor-mithril]

torchvision.transforms.v2.RandomErasing accepts a float or a sequence of floats for value, which is also mentioned in the documentation.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8769

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @ancestor-mithril!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[ancestor-mithril]

Checks require approval from a maintainer.

[NicolasHug]

Thanks for the PR @ancestor-mithril . I'm afraid this is introducing more issues: https://github.com/pytorch/vision/actions/runs/12088094679/job/33777630379?pr=8769

Note that a lot of typing annotations in torchvision are simply wrong, because they exist more to please torchscript than to please mypy (and those 2 tools often disagree).

[ancestor-mithril]

Note that a lot of typing annotations in torchvision are simply wrong, because they exist more to please torchscript than to please mypy (and those 2 tools often disagree).

I see. Maybe adding a type hint to self.value will fix this.