Skip to content

Conversation

@DhavalGojiya
Copy link
Contributor

Description

Migrated from Setuptools to the Hatchling build backend.

Hatchling is very fast, requires zero configuration, and provides good defaults.

Working with Setuptools is a painful process - we need to maintain external files like
MANIFEST.in to include/exclude files or folders in the source distribution, whereas
in Hatchling this process is straightforward and handled directly within the same
pyproject.toml.

Removed files

  • MANIFEST.in

Test Build

  • python -m build OR uv build

1. Source Distribution

sdists

2. Wheel Distribution

whl

Official Hatchling documentation:
https://hatch.pypa.io/

@DhavalGojiya
Copy link
Contributor Author

Now it looks like our GitHub Action workflows are more happier with uv than with tox 🤣🤣

@cclauss cclauss requested review from acdha, cclauss and claudep November 26, 2025 12:57
@claudep
Copy link

claudep commented Nov 26, 2025

Just for your information, I will stop watching this product as I don't use neither know anything about solr.

@cclauss cclauss removed the request for review from claudep November 26, 2025 13:06
@DhavalGojiya
Copy link
Contributor Author

Just for your information, I will stop watching this product as I don't use neither know anything about solr.

see-you-again

@acdha acdha merged commit ada7527 into django-haystack:master Dec 3, 2025
9 checks passed
@DhavalGojiya DhavalGojiya deleted the feat/hatchling-build-backend branch December 5, 2025 11:52
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.

4 participants