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

Use pure pyproject.toml setup for packaging #155

Merged
merged 2 commits into from
Feb 12, 2024

Conversation

bittner
Copy link
Member

@bittner bittner commented Feb 11, 2024

Phases out setup.py and requirements.txt in a quest to modernize packaging.

This PR also drops support for Python 3.6, which is not supported by newer versions of setuptools required to read all values out of pyproject.toml (e.g. name and authors).

@bittner bittner self-assigned this Feb 11, 2024
@bittner bittner force-pushed the feature/pure-pyproject-toml-packaging branch 2 times, most recently from d81da36 to 4433d0d Compare February 11, 2024 23:56
Modern setuptools that reads all attributes from `pyproject.toml` needs
Python 3.7+.
@bittner bittner force-pushed the feature/pure-pyproject-toml-packaging branch from 4433d0d to e3f1e44 Compare February 12, 2024 00:11
@bittner bittner merged commit 9699101 into main Feb 12, 2024
23 checks passed
@bittner bittner deleted the feature/pure-pyproject-toml-packaging branch February 12, 2024 00:17
@@ -8,7 +8,7 @@ envlist =
isort
pylint
# Python/Django combinations that are officially supported
py3{6,7,8,9,10}-django32
py3{7,8,9,10}-django32
Copy link
Contributor

Choose a reason for hiding this comment

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

Any particular reason for tox now? Figured with github actions, this was moot.

Copy link
Member Author

Choose a reason for hiding this comment

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

Tox is a tool that belongs to the development layer. It abstracts the details of running tests and linting away. Last but not least, it allows to run all the things locally, without the automation component.

I guess it's here to stay. Is there any good reason to get rid of it?

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