-
Notifications
You must be signed in to change notification settings - Fork 230
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
Drop support for EOL Python 2.6 #259
Conversation
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.
well done, thanks 👍
something broken in our bleeding edge code? related tests seem to be failing... |
Yep the pytestmaster and pytestfeatures build jobs are also failing on latest master: |
I suspect this is breaking because the output has changed and now includes the progress indicator in pytest-3.3, so the code which parses the output is not detecting what it intends to. |
Thanks, I've created #260 for that, as it's unrelated to this PR. |
@hugovk |
Pytest and Py have both dropped Python 2.6 as it's been EOL for 4 years.
Also remove some redundant Python 3.2 code (also EOL and looks like it's already dropped), some minor code cleanup, and add a Python version badge.
Here's a quick checklist that should be present in PRs:
Make sure to include reasonable tests for your change if necessary
We use towncrier for changelog management, so please add a news file into the
changelog
folder following these guidelines:Name it
$issue_id.$type
for example588.bugfix
;If you don't have an issue_id change it to the PR id after creating it
Ensure type is one of
removal
,feature
,bugfix
,vendor
,doc
ortrivial
Make sure to use full sentences with correct case and punctuation, for example: