Skip to content

Conversation

pmeier
Copy link
Collaborator

@pmeier pmeier commented Jan 6, 2023

I've run my IDE's spelling and grammar checker on our repository and it found quite a few improvements. With very few exceptions, the only changes happened in the docstrings or in code comments and thus don't affect the functionality at all. The one major exception is the file

https://github.com/pytorch/vision/blob/main/references/depth/stereo/vizualization.py

since it was flagged. I couldn't find the spelling "vizualization" in any dictionary. Thus, I've renamed it to visualization.py and fixed all imports of it. This of course should also not effect functionality, but has the potential if I botched the renaming.

Copy link
Collaborator Author

@pmeier pmeier left a comment

Choose a reason for hiding this comment

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

I've reverted all formatting changes in gallery/**/*. I'm in favor of fixing most of them, but we shouldn't do so in this PR. Overall, we now have -284,+281 changed lines. The asymmetry comes from three docstrings where I merged two lines into one. I've highlighted them below.

@pmeier pmeier marked this pull request as ready for review January 9, 2023 07:45
Copy link
Member

@NicolasHug NicolasHug left a comment

Choose a reason for hiding this comment

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

Thanks Philip,

Some minor comments but LGTM anyway.

I've renamed it to visualization.py

I guess that's fine. That may break direct links to this file that may exist somewhere on the web... but it's probably not a big deal.

for name in val_datasets:
if name == "kitti":
# Kitti has different image sizes so we need to individually pad them, we can't batch.
# Kitti has different image sizes, so we need to individually pad them, we can't batch.
Copy link
Member

Choose a reason for hiding this comment

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

I assume this comes from a hard rule that "so" must be preceded by a comma?
This doesn't work too well in practice IMO - but not worth nitpicking.

(I'm biased on this specific example because I think I was the one writing this comment)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm by no means an expert on the English language and thus I trusted the grammar checker here. But indeed, it told me

that "so" must be preceded by a comma

I don't know if this is just hard-coded or if this was a specific hint for the case at hand and in other situations the hint is not displayed.

@pmeier pmeier merged commit 7dc5e5b into pytorch:main Jan 11, 2023
@pmeier pmeier deleted the typos branch January 11, 2023 14:42
@github-actions
Copy link

Hey @pmeier!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

@pmeier pmeier added the other if you have no clue or if you will manually handle the PR in the release notes label Jan 11, 2023
facebook-github-bot pushed a commit that referenced this pull request Jan 13, 2023
Summary:
* fix typos throughout the code base

* fix grammar

* revert formatting changes to gallery

* revert 'an uXX'

* remove 'number of the best'

Reviewed By: YosuaMichael

Differential Revision: D42500907

fbshipit-source-id: d43295b8dc8f29f7ea89a659f2ca61749ac2b9b8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed other if you have no clue or if you will manually handle the PR in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants