-
Notifications
You must be signed in to change notification settings - Fork 30.9k
[TENTATIVE] Updating variable names HUGGINGFACE_CO_RESOLVE_ENDPOINT into HF_ENDPOINT. #16445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The documentation is not available anymore as the PR was closed or merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is purely cosmetic and internal, so I don't really see the point. We usually don't bother with renaming in those situations.
Is there any downsides to making the modifications ? Consistency in naming has a lot of merits, especially within HF ecosystem where the name is used in many different places and different repos. Here for instance, it took me several tries to find all variables that needed to be overridden in |
|
I think the renaming here makes sense as that's the variable name in other repositories; since there are no downsides, ok for me! |
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good change for me for consistency!
|
Ok, merging, feel free to revert if anything breaks ! |
This reverts commit 4f3a14e.
) This reverts commit 4f3a14e.
) This reverts commit 4f3a14e.
What does this PR do?
HUGGINGFACE_CO_RESOLVE_ENDPOINTis deprecated and will go away in favorof
HF_ENDPOINT.In order to maximize consistency, this PR renames the variable name itself.
This is tentative, since there might have been reasons to keep the old name for
the variable.
Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@LysandreJik @sgugger