Python 3.3.x has reached end-of-life. This is its final release. It is a security-fix source-only release.
Python 3.3.0 was released on 2012-09-29 and has been in security-fix-only mode since 2014-03-08. Per Python Development policy, all support for the 3.3 series of releases ended on 2017-09-29, five years after the initial release. This release, Python 3.3.7, was the final release for the 3.3 series.
After 2017-09-29, we no longer accept bug reports nor provide fixes of any kind for Python 3.3.x (third-party distributors of Python 3.3.x may choose to offer their own extended support). Because 3.3.x has long been in security-fix mode, 3.3.7 may no longer build correctly on all current operating system releases and some tests may fail. If you are still using Python 3.3.x, we strongly encourage you to upgrade to a more recent, fully supported version of Python 3; see https://www.python.org/downloads/.
It was too much of a pain to support. It would require exclusion of py3.3 from the version matrix and figuring out specifically build it on its own as we run docs against our builds. Its not really critical to have both platforms run the doc generation but nice to have. Generally not worth investing any further effort, it is still usable, just won't be officially tested.
Coverage increased (+0.1%) to 58.514% when pulling bb66f1f9233569799308d1b40a55ec6c4013c888 on neomonkeus:fix_appvoyer into 0f37450addf2ae5d42b25af580ae5544a24a03b5 on niftools:develop.
@niftools/pyffi-reviewers
Overview
Reworks life-cycle management
Fixes Known Issues
Failure introduced to CI automation #51
Documentation
n/a
Testing
Runs through both CI platforms fully for entire version matrix
Manual
Manually tested dependency installation via pip and setup.py
Automated
Existing test suite runs via CI automation
Additional Information
Dropped python 3.3 support. https://www.python.org/downloads/release/python-337/
It was too much of a pain to support. It would require exclusion of py3.3 from the version matrix and figuring out specifically build it on its own as we run docs against our builds. Its not really critical to have both platforms run the doc generation but nice to have. Generally not worth investing any further effort, it is still usable, just won't be officially tested.