-
Notifications
You must be signed in to change notification settings - Fork 19
Use base class distutils.cmd.Command if/when necessary
#89
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
Conversation
| strategy: | ||
| matrix: | ||
| python-version: ['3.6', '3.7'] | ||
| python-version: ['3.7', '3.8', '3.9'] |
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.
If there isn't CI running on 3.6 I'm reluctant to say setupmeta is compatible with it. Am I reading this right?
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.
Tests pass with 3.6, but there is some unrelated failure on py3.6 venv creation currently on GH actions. setupmeta's is still py3.6 compatible, but it is getting harder to exercise py3.6 indeed (including locally, where you can't use tox-uv for exameple, must use tox v3)
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.
Bumped python_requires to 3.7+. You're right, no point in trying to keep 3.6 around any longer.
| skip_missing_interpreters = true | ||
|
|
||
| envlist = py{37,38,39,310,311,312,313}, coverage, docs, style, security | ||
| indexserver = |
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.
maybe include a comment about why this apparent no-op is here?
Adapted
checkcommand redefinition for setuptools 77.0.3.See pypa/setuptools#4902