Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Drop support for Python 2.6 #250
I've previously advocated for keeping 2.6-compatibility, but have since changed my mind. There are lots of small inconveniences when restricted to the 2.6/3.x common subset. In particular, this drastically restricts the choice of upstream modules.
Old versions of gcovr will of course continue to work. This also means there will never be a gcovr version that works well on Windows with Python 2.6, but since that OS doesn't bundle Python such a
Now is a good time to drop support since the next release will likely be 4.0, and we already have a number of other somewhat breaking changes (e.g. different installation procedure). One biggie that is still pending is improved Windows filtering (see #191). I would not like to be locked in to Python 2.6 for the rest of gcovr 4.x.
Request for comments: Are there any problems that I missed? Will this make someone else's life much more difficult? I will wait at least 2 weeks before applying this change in order to provide enough time for feedback.
@@ Coverage Diff @@ ## master #250 +/- ## ======================================= Coverage 88.76% 88.76% ======================================= Files 13 13 Lines 1478 1478 Branches 267 267 ======================================= Hits 1312 1312 Misses 108 108 Partials 58 58
Here's the pip installs for gcovr from PyPI for last month, 2.6 is little used:
pypinfo --start-date -42 --end-date -12 --percent --pip --markdown gcovr pyversion
Remember to update
python_requires in setup.py,
python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*', would also skip 3.0-3.3.