Move the source of truth of kaggle-api development to this repository

[Philmod]

Changes

• It uses hatch, for example hatch run compile to generate the python files to release to pypi
• The generated code is checked-in so that users can pip install from source, as before this change
• The important files to review are:
  • the new README.md
  • the tools/GeneratePythonLibrary.sh that was modified

Next

• Remove code from main kaggle repo
• Internal documentation for release, etc...

Ideas for medium-term

• Lint / Coverage (example: https://github.com/Kaggle/kagglehub?tab=readme-ov-file#lint--format)
• Unit tests (run on PR)
• Integration tests (run on PR)
• Script to change the version across the 4 files

Bug

http://b/325046928

[erdalsivri]

LGTM!

[stevemessick]

I made lots of comments about line breaks. Those can be considered optional. I did clean up the language in a few places and those should be included.

[stevemessick]

Also, note that when you first see my comments you may have a bunch that are collapsed. I had to click the line that said there were 26 hidden comments to see them all.

Edit: even then, there were still six collapsed under another See more... block.

[neshdev]

LGTM.

I would have assume that the delta between the repos to be a lot smaller. Has the repo not been synced for a while?

Also, is it possible to get ride of the formatting changes?

[Philmod]

LGTM.

I would have assume that the delta between the repos to be a lot smaller. Has the repo not been synced for a while?

Also, is it possible to get ride of the formatting changes?

The diff in the kaggle/ directory are indeed mostly formatting changes, but unclear where they come from.