-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
artifacts: Bring back name_is_compatible
.
#9972
Conversation
Codecov ReportAttention:
... and 2 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
@@ -38,6 +38,17 @@ def check_name_format(name: str) -> None: | |||
) from exc | |||
|
|||
|
|||
def name_is_compatible(name: str) -> bool: | |||
from gto.constants import assert_name_is_valid |
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.
Was it only importing it or using also? If the former then a noop stub should do. But either way need a comment here with a link so we know this is only kept because of dvclive and can drop it later.
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.
Was it only importing it or using also?
Actually using
Unfortunately, DVCLive was importing this function so I am bringing back the name for backwards compatibility.
b6065ce
to
71cb7a6
Compare
Unfortunately, DVCLive was importing this function so I am bringing back the name for backwards compatibility.
See iterative/dvclive#715