-
Notifications
You must be signed in to change notification settings - Fork 46
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
Conversation
d81da36
to
4433d0d
Compare
Modern setuptools that reads all attributes from `pyproject.toml` needs Python 3.7+.
4433d0d
to
e3f1e44
Compare
@@ -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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
Phases out
setup.py
andrequirements.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).