notebook API renames + install pin bump for tracebloc_package 0.7.0#7
Draft
aptracebloc wants to merge 2 commits intomainfrom
Draft
notebook API renames + install pin bump for tracebloc_package 0.7.0#7aptracebloc wants to merge 2 commits intomainfrom
aptracebloc wants to merge 2 commits intomainfrom
Conversation
Aligns with the optional-dependency-groups change shipping in tracebloc-py-package 0.6.33. Default install no longer bundles every ML framework — users pick the extra that matches their setup. - README.md: 3-line extras table in the local-setup section. - notebooks/traceblocTrainingGuide.ipynb cell 3: switch install cmd to [pytorch] as the most common setup; comment points at [tensorflow] and [all]. DO NOT MERGE until tracebloc_package 0.6.33 is live on real PyPI. Currently 0.6.33 is only on TestPyPI. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Builds on top of the install-extras change (eeae340) and broadens scope for the upcoming tracebloc_package 0.7.0 release. Notebook changes (notebooks/traceblocTrainingGuide.ipynb): - Cell 3 install pin: >=0.6.33 -> >=0.7.0 - Cell 11: user.uploadModel(MODEL_PATH) -> user.upload_model(MODEL_PATH) - Cell 12 (markdown docs example): same uploadModel rename - Cell 14: user.linkModelDataset(DATASET_ID) -> user.link_model_dataset(DATASET_ID) - Cell 16 (reference table): experimentName, learningRate, getTrainingPlan, resetTrainingPlan -> experiment_name, learning_rate, get_training_plan, reset_training_plan - Cell 17: experimentName + getTrainingPlan call sites updated README.md: pip install lines bumped from >=0.6.33 to >=0.7.0 across all three extras (pytorch, tensorflow, all). Static rewrite only; the notebook was not executed (requires real workspace credentials). All deprecated symbols touched here have deprecation aliases on the Python side, so callers using the old names would still work but emit DeprecationWarning. Supersedes #4 (which was scoped only to the 0.6.33 install-extras migration). The 0.6.33 release path is being collapsed into 0.7.0 now that SDK.2/3 work has landed on develop, so this PR ships both changes together. Cannot merge until tracebloc_package 0.7.0 is published to real PyPI — same merge-coordination block as #4. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
aptracebloc
changed the title
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
2 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.
tracebloc_package 0.7.0ships to real PyPIThe notebook's install cell pins
>=0.7.0. If this PR merges before 0.7.0 is published, every user running the guide will hit "Could not find a version that satisfies the requirement."Summary
Combines two notebook updates into a single 0.7.0-targeted PR:
[pytorch],[tensorflow],[all]) shipping intracebloc_package 0.6.33+. Pin bumped to>=0.7.0since 0.6.33 is being collapsed into 0.7.0 (SDK.2/3 breaking-change work landed ontracebloc_package@developand the next public release is 0.7.0).Changes
notebooks/traceblocTrainingGuide.ipynbtracebloc_package[pytorch]>=0.6.33tracebloc_package[pytorch]>=0.7.0user.uploadModel(MODEL_PATH)user.upload_model(MODEL_PATH)user.uploadModel(MODEL_PATH, weights=True)(docs)user.upload_model(...)user.linkModelDataset(DATASET_ID)user.link_model_dataset(DATASET_ID)experimentName,learningRate,getTrainingPlan,resetTrainingPlan(table)trainingObject.experimentName(...)+trainingObject.getTrainingPlan()experiment_name(...)+get_training_plan()README.mdThree install lines bumped from
>=0.6.33to>=0.7.0.Why all method calls survive (no
TypeErrorrisks)DATASET_IDandMODEL_PATHare passed positionally — none of the SDK.2 kwarg renames (datasetId→dataset_id, etc.) applydeprecated_method_aliason the Python side, so the camelCase variants still work and just emitDeprecationWarning. This PR is about cleaning up the user-facing surface, not unblocking any breakageWhy this supersedes #4
@LukasWodka's #4 was scoped to 0.6.33 install-extras only. The 0.6.33 release path is being collapsed into 0.7.0 now that the SDK.2/3 breaking-change work has landed on
tracebloc_package@develop. Cleaner to ship both changes in one PR than coordinate two sequential start-training releases.#4's commit (
eeae340) is preserved as the parent of this branch — Lukas's authorship on that commit is intact.Merge coordination
Same as #4 — needs same-day with:
tracebloc/tracebloc-py-package@v0.7.0going live on real PyPItracebloc/docsPR for the Mintlify setup guidetracebloc/tracebloc-website-mainPR for the homepage quick-start snippetTest plan
Static edits only — notebook was not executed. Pre-merge checklist for whoever runs the guide end-to-end:
🤖 Generated with Claude Code