SK-2833: Add backward-compatible deprecation shims for update_log_level and FileUploadRequest#244
Merged
saileshwar-skyflow merged 6 commits intoMay 20, 2026
Conversation
aadarsh-st
approved these changes
May 20, 2026
skyflow-bharti
approved these changes
May 20, 2026
saileshwar-skyflow
merged commit f30e8c9
into
saileshwar/SK-2813-python-v2-code-clean-up-and-fixes
4 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Customers upgrading from older SDK versions would hit silent failures (AttributeError, wrong column uploads) with no guidance on what changed
Python's DeprecationWarning mechanism and @deprecated decorator let us keep old APIs working while steering developers to the new interfaces before removal
Outcome
Skyflow.update_log_level() and the old FileUploadRequest(table, skyflow_id, column_name) positional style both still work — existing code won't break on upgrade
Developers see compile-time IDE strikethrough and runtime console warnings with exact migration instructions, backed by 100% unit test coverage on the public client interface