Migrate build system to pyproject.toml and uv

[sarang-pratham]

Summary
This PR modernizes the project’s Python packaging and dependency management using uv
. It replaces legacy setup.py and requirements.txt handling with a clean pyproject.toml config.

Changes

• Migrated metadata and dependencies from setup.py to pyproject.toml
• Consolidated optional dependencies under [project.optional-dependencies]
• Verified compatibility by running all test suites (pytest)

Notes

Verified locally with:

uv sync --all-extras
uv run pytest

147 passed, 31 skipped, 4 warnings

[ekzhu]

@bhimrazy could you work with @sarang-pratham here to review this PR?

[Copilot]

Pull Request Overview

This PR modernizes the Python packaging configuration by migrating from setup.py to the PEP 517-compliant pyproject.toml format and adds documentation for the uv build system.

• Replaced legacy setup.py with declarative pyproject.toml configuration
• Added .python-version file specifying Python 3.13
• Documented development setup using uv in README

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 3 comments.

File	Description
setup.py	Simplified to minimal shim calling setup() with configuration now in pyproject.toml
pyproject.toml	New declarative package configuration with all metadata, dependencies, and optional extras
README.rst	Added development setup instructions for using uv build system
.python-version	Specifies Python 3.13 as the default version for development

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bhimrazy]

@bhimrazy could you work with @sarang-pratham here to review this PR?

Sure @ekzhu

[bhimrazy]

@ekzhu, I was wondering if it would be possible to grant edit permissions. With that, I can run the CI and make the necessary changes as well.

[ekzhu]

@ekzhu, I was wondering if it would be possible to grant edit permissions. With that, I can run the CI and make the necessary changes as well.

I am figuring out the permission system for GitHub personal projects -- it is not as fine-grained as I'd like. Currently, once a user contributed to the repo, the CI will automatically run for that user. So in case this PR gets stalled you can start another PR and the CI will run okay.

[sarang-pratham]

@ekzhu @bhimrazy
I was thinking if this https://github.com/nektos/act is something you guys would recommend using to test gh actions locally before pushing ?

[bhimrazy]

Hi @sarang-pratham, I’ve opened another PR (#271) so that the CI can run and the changes can be properly tested. I’ve also included your commits there.

It’s (#271) quite a big one though — not sure if @ekzhu will like it.

[sarang-pratham]

Hi @sarang-pratham, I’ve opened another PR (#271) so that the CI can run and the changes can be properly tested. I’ve also included your commits there.

It’s quite a big one though — not sure if @ekzhu will like it.

Okay, so this Open PR might not be relevant anymore - can we decline / close this ? @bhimrazy

cc: @ekzhu

[ekzhu]

Thanks. I will close this one.