-
Notifications
You must be signed in to change notification settings - Fork 910
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
Deprecate (mark for future removal) get_pkg_version
from the public API
#3789
Comments
One question here, we tend to do the breaking change later in This is not important for this particular issue, because I think no one use it (hopefully), but it is a valid question for what should we do in general? |
Yes |
Do we need a subticket for deprecation? Or this is ready to go in backlog
grooming.
…On Thu, 11 Apr 2024, 15:32 Juan Luis Cano Rodríguez, < ***@***.***> wrote:
should we add the deprecated warnings earlier in 0.19 to inform user?
Yes
—
Reply to this email directly, view it on GitHub
<#3789 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELAWL6RQQZNPW2IXZXHCFDY42NJXAVCNFSM6AAAAABF4VKBCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZHAZTINBQGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'd say let's rename this ticket to "Deprecate |
get_pkg_version
from the public APIget_pkg_version
from the public API
Actually the tests are obsoleted and we should remove it altogether |
Funny bit of insight found in the source code of
Not sure how up to date it is though (the thread is from 2019). |
Context
kedro/kedro/framework/cli/utils.py
Lines 204 to 218 in a91ccdb
I just check again, this function is not used anywhere in framework, but only tests. (last change is 4 years ago). Maybe at some points it was used for
kedro build-reqs
? I suggest we deprecate this function since it's a public function and move it to test.Originally posted by @noklam in #2912 (comment)
Remove the function from public API and move it to test only.
The text was updated successfully, but these errors were encountered: