Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Migrate build to use hatchling #241

Merged
merged 9 commits into from
Aug 23, 2024
Merged

Conversation

matthewfeickert
Copy link
Member

@matthewfeickert matthewfeickert commented Aug 23, 2024

* Use hatchling and hatch-vcs as build system.
* Remove setuptools and related files from repository.
   - Remove setup.py, setup.cfg, MANIFEST.in.
   - Remove check-manifest from 'develop' extra.
* Remove setuptools install from CI.
* Remove check-manifest checks from CI.
* Add .flake8 file as flake8 doesn't support pyproject.toml.

It is worth noting that almost all of the PR (the first commit) was done automatically by

hatch new --init

! That's awesome!

@matthewfeickert matthewfeickert merged commit 5168e71 into main Aug 23, 2024
13 checks passed
@matthewfeickert matthewfeickert deleted the build/migrate-to-hatch branch August 23, 2024 21:37
@matthewfeickert matthewfeickert changed the title ci: Migrate build to use hatchling build: Migrate build to use hatchling Aug 23, 2024
matthewfeickert added a commit that referenced this pull request Aug 23, 2024
* Use hatchling and hatch-vcs as build system.
   - Done mostly automatically with 'hatch new --init'.
* Remove setuptools and related files from repository.
   - Remove setup.py, setup.cfg, MANIFEST.in.
   - Remove check-manifest from 'develop' extra.
* Remove setuptools install from CI.
* Remove check-manifest checks from CI.
* Add .flake8 file as flake8 doesn't support pyproject.toml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant