Skip to content

Switch to hatchling build-backend - #90

Merged
mauvilsa merged 2 commits into
rr-:masterfrom
LecrisUT:PEP621
Jul 7, 2025
Merged

mauvilsa merged 2 commits into
rr-:masterfrom
LecrisUT:PEP621

Conversation

@LecrisUT

@LecrisUT LecrisUT commented Sep 9, 2024

Copy link
Copy Markdown
Contributor

I would recommend not using poetry, particularly since using any other PEP517 compliant build backend makes things so much easier.

I have kept the dev dependency as-is so you can simply run pip install .[dev], but I would recommend against using that because the only dependency there is pre-commit, which is better if you have it installed and managed globally instead of within the venv. Otherwise the other dependencies are split like that because test dependencies are often required by packagers, and docs can be used for the specific documentation build backend.

I would also recommend to drop Python<3.8, and even python 3.8 at this point.

@mauvilsa mauvilsa left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I have also had problems with poetry and think it would be good to replace it. Thanks for contributing!

@mauvilsa
mauvilsa merged commit aaf857d into rr-:master Jul 7, 2025
@LecrisUT

LecrisUT commented Jul 7, 2025

Copy link
Copy Markdown
Contributor Author

Might want to update the readme at some point. Happy to see this getting some attention

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