Skip to content

feat: add python bindings - #54

Merged
qvalentin merged 3 commits into
ngalaiko:masterfrom
5trigen:feat/add-python-bindings
Oct 2, 2026
Merged

qvalentin merged 3 commits into
ngalaiko:masterfrom
5trigen:feat/add-python-bindings

Conversation

@5trigen

@5trigen 5trigen commented May 29, 2026

Copy link
Copy Markdown

This PR adds Python bindings. Much of this code is adapted from tree-sitter-python.

  • The C-bindings under bindings/python/ are defined analogously to those in tree-sitter-python with a single test under bindings/python/tests
  • setup.py is also copied over with names changed.
  • pyproject.toml contains the metadata of the pypi package, which I've tried to sync with the Cargo.toml file. Like Cargo.toml, it contains the version of the package as a hardcoded string. This file should therefore be edited on future version bumps.
  • I've added a step to the ci pipeline to run the python bindings test

@5trigen
5trigen marked this pull request as draft May 29, 2026 14:36
@qvalentin

Copy link
Copy Markdown
Collaborator

@5trigen looking good. Can you fix the ci pipeline?

@5trigen
5trigen force-pushed the feat/add-python-bindings branch 2 times, most recently from 6ddec35 to bc8f862 Compare June 19, 2026 13:04
@5trigen
5trigen force-pushed the feat/add-python-bindings branch from bc8f862 to 328468a Compare June 19, 2026 13:05
@5trigen

5trigen commented Jun 19, 2026

Copy link
Copy Markdown
Author

@5trigen looking good. Can you fix the ci pipeline?

Done, I've used a pipeline template that could also be used for the go tests. I haven't touched them, because I think its out of scope for this PR, but if you want I could make a follow up PR to streamline the pipeline a bit.

@5trigen
5trigen marked this pull request as ready for review June 24, 2026 12:20
@qvalentin
qvalentin merged commit 06b2fd2 into ngalaiko:master Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants