Skip to content

Migrate from setuptools to hatch#809

Open
Yonghui-Lee wants to merge 2 commits intofsspec:mainfrom
ankitaluthra1:hatch
Open

Migrate from setuptools to hatch#809
Yonghui-Lee wants to merge 2 commits intofsspec:mainfrom
ankitaluthra1:hatch

Conversation

@Yonghui-Lee
Copy link
Copy Markdown
Collaborator

@Yonghui-Lee Yonghui-Lee commented Apr 15, 2026

Migrate from the legacy setuptools and versioneer to hatch. This aligns the project with modern Python packaging standards.

Key Changes

Build System & Versioning

  • Migrate to Hatch: Switched the build backend to hatchling and enabled hatch-vcs for dynamic versioning based on Git tags.
  • Consolidate Configuration: Added project metadata, dependencies, and tool configurations to pyproject.toml.

Cleanup of Legacy Files

  • Remove setup.py: Dropped the legacy installation script in favor of declarative configuration in pyproject.toml.
  • Remove Versioneer: Deleted versioneer.py and the generated gcsfs/_version.py.
  • Remove MANIFEST.in: Hatch automatically handles file inclusion, making this file redundant.
  • Remove .isort.cfg: Configuration has been moved to pyproject.toml.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.03%. Comparing base (5596df9) to head (0299219).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #809      +/-   ##
==========================================
+ Coverage   79.55%   85.03%   +5.48%     
==========================================
  Files          16       15       -1     
  Lines        3042     2680     -362     
==========================================
- Hits         2420     2279     -141     
+ Misses        622      401     -221     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Yonghui-Lee Yonghui-Lee marked this pull request as draft April 15, 2026 04:50
@Yonghui-Lee Yonghui-Lee marked this pull request as ready for review April 15, 2026 08:09
@zhixiangli
Copy link
Copy Markdown
Contributor

Could you please verify that the ci.yml, benchmarks-cloudbuild.yaml, and cloudbuild/e2e-tests-cloudbuild.yaml files are still functional?

@Yonghui-Lee
Copy link
Copy Markdown
Collaborator Author

Could you please verify that the ci.yml, benchmarks-cloudbuild.yaml, and cloudbuild/e2e-tests-cloudbuild.yaml files are still functional?

I have run github ci, could build e2e tests and cloud build benchmark. The results look good to me.

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