Update protos and release 0.1.17 by nl917 · Pull Request #31 · Kaggle/kaggle-sdk-python

nl917 · 2026-04-03T21:27:44Z

Update proto to include newest change from benchmarks

dolaameng

LGTM. Thank you @nl917 !

Would like @stevemessick to take a look.

erdalsivri · 2026-04-06T19:02:38Z

kagglesdk/__init__.py

@@ -1,4 +1,4 @@
-__version__ = "0.1.16"
+__version__ = "0.1.17"


I don't know the release process of kaggle-sdk but I suppose there is some manual step here to actually publish this package. I don't know how kaggle-cli imports this package. It used be a manual copy but I am not sure if that has changed. @stevemessick knows better

Just realized Steve is OOO this week. Requested review from Jonathan instead

Yes @nl917 I think these are experimental features only with placeholder code but not real implementation? Checking in the code is to help unblock downstream application. But if this got published to pypi, we probably just wait till everything is implemented by @andrewmwang first.

I'm also not super familiar with recent implementations/updates to the sdk but I can do a quick look over and see if anything stands out

Once this is merged and a new version of kagglesdk is published to pypi (docs here: https://g3doc.corp.google.com/cloud/kaggle/apis/g3doc/kagglesdk.md#how-to-push-to-pypi), the way Kaggle CLI gets the new package is by bumping it's dependency here: https://github.com/Kaggle/kaggle-cli/blob/main/pyproject.toml#L27

it is currently set to 0.1.16 and we'd change that to 0.1.17.

then we'd need to do a release of Kaggle CLI so our users can pick up the new version. we can test that Kaggle CLI deps pull in the new kagglesdk version locally by:

hatch env remove default hatch run kaggle --help

(that 2nd line could be any command. we just want to call something to rebuild the CLI)

it'd be good to run the Kaggle CLI tests too to make sure everything is working: https://github.com/kaggle/kaggle-cli?tab=readme-ov-file#tests

btw this assumes in your local CLI env you didn't do anything like pip install kagglesdk --break-system-packages (b/c then it would pull from that global install vs. try to install based on the .toml definition)

dolaameng · 2026-04-06T23:26:32Z

kagglesdk/benchmarks/types/benchmark_tasks_api_service.py

+      The slug for the task without the user's namespace. (ex: my-task instead of
+      username/my-task). This should match the slug in the kaggle-benchmarks
+      decorator in the code.
+    text (str)


@andrewmwang Can you confirm this the text for the .py source code? And on the server side, a .py file with delimiters like # %% will be converted to a ipython notebook properly?

dolaameng · 2026-04-06T23:45:13Z

kagglesdk/benchmarks/types/benchmark_tasks_api_service.py

+  r"""
+  Attributes:
+    task_slugs (ApiBenchmarkTaskSlug)
+    model_slugs (str)


@nl917 @andrewmwang what's the behavior here when model_slugs is empty list []. Will it run on all models, or no models?

should we make it so that it runs on the default model? that might be the most common option

should we make it so that it runs on the default model? that might be the most common option

From a client perspective, the -m here works like a model filter, so if nothing specified, it's probably more intuitive to default to run ALL models. Wdyt?

My concern is that the model list will only keep increasing. And right now we can only do five runs at a times. will it be too laggy if we run it on all models? I feel like we don't want to make it too easy to do this.

Yes that's a good point. In that case can go back to default model.

stevemessick

RSLGTM -- I don't usually read the code from kapigen.

jmasukawa

Thanks for waiting for my datasets changes. LGTM!

@goeffthomas

…ds (#958) Leverages changes to `DatasetApiService/V1/UpdateDatasetMetadataHandler` and `DatasetApiService/V1/GetDatasetMetadataHandler` to accept expected update frequency and user specified sources. Wait before merging: - [x] MT changes are deployed: Kaggle/kaggleazure#41349 - [x] Correct set of kagglesdk changes are made / merged and release is pushed: Kaggle/kaggle-sdk-python#31 Other changes: - Pin `virtualenv` version so `./docker-hatch` works - Run lint / format before making any changes (there was drift) - Docs updates for datasets / datasets metadata Local testing: - [screencast](http://go/scrcast/NTI4NTQxMDQ2ODAwMzg0MHwwNjg0MjViNC1iNQ) cc: @goeffthomas http://b/500108129

nl917 added 2 commits April 3, 2026 21:27

add new generated files

d435a80

update-version

f6aa41e

nl917 changed the title ~~add new generated files~~ Update protos and release 0.1.17 Apr 3, 2026

nl917 requested review from andrewmwang and rosbo and removed request for rosbo April 3, 2026 21:34

remove unneeded changes

f53427f

nl917 force-pushed the update-sdk branch from e671151 to f53427f Compare April 3, 2026 21:42

nl917 requested a review from dolaameng April 3, 2026 21:42

dolaameng requested a review from stevemessick April 3, 2026 22:58

dolaameng approved these changes Apr 3, 2026

View reviewed changes

nl917 requested a review from erdalsivri April 6, 2026 18:56

erdalsivri reviewed Apr 6, 2026

View reviewed changes

nl917 requested review from jeward414 and removed request for stevemessick April 6, 2026 19:05

dolaameng reviewed Apr 6, 2026

View reviewed changes

stevemessick approved these changes Apr 7, 2026

View reviewed changes

nl917 added 2 commits April 8, 2026 20:31

update the library with newest change

4ea0746

remove not needed

03209cb

jmasukawa approved these changes Apr 8, 2026

View reviewed changes

nl917 merged commit 6895c97 into main Apr 8, 2026
2 checks passed

nl917 deleted the update-sdk branch April 8, 2026 21:37

This was referenced Apr 8, 2026

WIP: Update kagglesdk to test new Kaggle CLI functionality. #32

Closed

Change get / update dataset metadata to handle two more metadata fields Kaggle/kaggle-cli#958

Merged

Conversation

nl917 commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dolaameng left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jeward414 Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jmasukawa Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nl917 Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stevemessick left a comment

Choose a reason for hiding this comment

Uh oh!

jmasukawa left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

nl917 commented Apr 3, 2026 •

edited

Loading

jeward414 Apr 6, 2026 •

edited

Loading

jmasukawa Apr 7, 2026 •

edited

Loading

nl917 Apr 7, 2026 •

edited

Loading