-
Notifications
You must be signed in to change notification settings - Fork 638
Remove support for Python 3.4 + update testing dependencies #532
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
Codecov Report
@@ Coverage Diff @@
## develop #532 +/- ##
========================================
Coverage 64.46% 64.46%
========================================
Files 63 63
Lines 5651 5651
========================================
Hits 3643 3643
Misses 2008 2008 |
setup.py
Outdated
@@ -98,7 +97,7 @@ | |||
|
|||
# Installation | |||
# see https://www.python.org/dev/peps/pep-0345/#version-specifiers | |||
python_requires=">=2.7,!=3.0,!=3.1,!=3.2,!=3.3", | |||
python_requires=">=2.7,!=3.0,!=3.1,!=3.2,!=3.3,!=3.4", |
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.
Does this mean it won't even try to install on Python 3.4? Do we want that?
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.
That's at least how we did it with Python 3.0-3.3.
Does this mean it won't even try to install on Python 3.4?
And yes, apparently that's how it should be handled.
I guess we don't want that, since it might work and we just don't guarantee it. But then let's remove everything except python_requires=">=2.7"
, 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.
I'm just surprised that no one complained about 3.0 through 3.3 not working! I'd have thought we'd get some issues if we remove support for Python 3.4
... but then again people running Python3.4 probably aren't going to be running the latest release of python-can either.
I'm okay with you adding the !=3.4
We could have a look at this as well: https://setuptools.readthedocs.io/en/latest/setuptools.html#automatic-script-creation |
setup.py
Outdated
}, | ||
|
||
# Installation | ||
# see https://www.python.org/dev/peps/pep-0345/#version-specifiers | ||
python_requires=">=2.7,!=3.0,!=3.1,!=3.2,!=3.3,!=3.4", |
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.
@hardbyte This commit now removed it ... and is merged into develop.
This removes support for Python 3.4, since it will reach EOL on 2019-03-16 (=next week).
It also updates the testing tools to their current versions.