Ditch setuptools

Open
#238 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
53/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
build-system

Research direction

Start by reading the project's packaging configuration and compare how hatchling and uv_build would fit the current build setup; the issue names no specific files or tests. Choose and document a migration path, then verify the package can still be built and installed with the replacement backend.

Written by the indexing model from the issue text.

Description

The package currently uses setuptools. setuptools has a number of annoying warts - I'd be interested in switching off it.

Two clear options:

  • hatchling - somewhat ubiquitous/common
  • uv_build - have used in other projects, has gone well
Dominant language
Python
Stars
432
Forks
56
Avg merge
1d 12h
Merged PRs (30d)
12

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jfhbrook/pyee

All issues in jfhbrook/pyee

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.