Fix docstring for 'fill' in transforms without 'padding_mode'

[abhitorch81]

Summary

This PR applies the minimum docstring fix for fill, as discussed in #9149.

Replaced:

Pixel fill value used when the padding_mode is constant.

With:

Pixel fill value used for pixels outside the image boundary.

This corrects the docstring in transforms like ElasticTransform, RandomAffine, etc., which do not have a padding_mode parameter.

No functional changes made.

Fixes: #9149

Hi @diaz-esparza — no worries at all, and thank you for your thoughtful message!

I’ve gone ahead and applied the minimum docstring fix as discussed in the issue, specifically removing the misleading reference to padding_mode and updating the fill parameter description for clarity.

You’re of course very welcome to iterate or build on top of it — especially if you’re still considering the more advanced version as a feature enhancement.

Appreciate your openness to feedback — and honestly, your explanation and tone were already clear and friendly! Looking forward to your thoughts on the PR

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures

As of commit e8571e3 with merge base ce5b26a ():

NEW FAILURES - The following jobs have failed:

• CMake / windows (windows.g5.4xlarge.nvidia.gpu, cuda, 12.6) / windows-job (gh)
  Process completed with exit code 1.
• Docs / build / linux-job (gh)
  RuntimeError: Command docker exec -t 84e9940c3843fe08bc6287517aa10d20995d820f794b42e3fac74e85f6a11ffb /exec failed with exit code 2

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

[diaz-esparza]

pixels outside the image boundary is a really nice way of putting it, props on that!

On that note though, please be careful with a few things about the change. Mainly, you've also altered the Pad and RandomCrop docstrings, and I think it's important on those two to keep the padding_mode reference given that the fill parameter is only useful when the other one is set to "constant". Both reverting the change or putting [...] for pixels outside the image boundary when the ``padding_mode`` is constant should be fine!

Also I think there's a misindentation on the RandomAffine docstring and an extra line in RandomCrop, please be on the lookout for that kind of stuff :)

[abhitorch81]

pixels outside the image boundary is a really nice way of putting it, props on that!

On that note though, please be careful with a few things about the change. Mainly, you've also altered the Pad and RandomCrop docstrings, and I think it's important on those two to keep the padding_mode reference given that the fill parameter is only useful when the other one is set to "constant". Both reverting the change or putting [...] for pixels outside the image boundary when thepadding_modeis constant should be fine!

Also I think there's a misindentation on the RandomAffine docstring and an extra line in RandomCrop, please be on the lookout for that kind of stuff :)

I will keep that in mind and update the PR.

[scotts]

Agreed with @diaz-esparza that we need to make sure that when there is a padding_mode parameter, we explicitly mention it in the docstring.

[abhitorch81]

Agreed with @diaz-esparza that we need to make sure that when there is a padding_mode parameter, we explicitly mention it in the docstring.

I will work on it.

[scotts]

The indentation here is wrong, which is causing the docs builds to fail. I think it's just a missing space.

[scotts]

Let's fix the spacing so that the docs build successfully.

[abhitorch81]

I will do that.