Removed Python 2.6 & 3.3

[engnadeau]

• DEPRECATION: Python 2.6 is no longer supported by the Python core team

• New build jobs are failing only with Python 2.6 (e.g., https://travis-ci.org/yaml/pyyaml/jobs/309566015)

• Update 2017-12-08

  • Added Python 3.3 removal to this PR, as it is also EoL (https://docs.python.org/devguide/index.html#branchstatus)

[hugovk]

👍

Don't forget to remove from here:

https://github.com/yaml/pyyaml/blob/master/.travis.yml#L9-L10
https://github.com/yaml/pyyaml/blob/master/setup.py#L30
https://github.com/yaml/pyyaml/blob/master/setup.cfg#L25

[engnadeau]

@hugovk thanks for the reminder! Travis passes now

[engnadeau]

@alex @dstufft @hugovk is there anything else you'd like me to look into?

[hugovk]

Looks good.

It would be good to add this to setup() in setup.py, so pip will install the correct distribution for the user's Python version:

python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*',

[alex]

I'd encourage the PyYAML maintainers to land this in a separate release from the current master. That is because master includes making PyYAML safe by default, and I don't want that to be denied to people who are (depressingly) insistent on using 2.6.

[engnadeau]

@hugovk following your python_requires suggestion, I also noted that Py3.3 is EoL as well. The following commits also clean this up:

• 27ad57c
• 0dc2292
• 4180a96

However, if you prefer, I can move this into its own PR

@alex, Python 2.6 builds are not passing on master...

• https://travis-ci.org/yaml/pyyaml/jobs/309566015#L497-L521
• https://travis-ci.org/yaml/pyyaml/jobs/307595549#L492-L519
• Etc, see other recent PRs

[alex]

They're failing because we install a version of wheel that's too new. I'm not saying this is good, I'd be very happy for Python 2.6 to die a firey death, but given the choice between YAML RCEs and Python2.6 fixes, I want everyone to get the RCE fixes.

[hugovk]

As a compromise, how about making a release quite soon with the RCE fixes, then merging this right after release?

[alex]

That sounds great to me. To the PyYAML maintainers: if there's anything I can do to help get a release out, please let me know!

[engnadeau]

@hugovk is there an open issue for YAML RCEs that we can link this PR to?

[hugovk]

Let's ask @alex.

[alex]

#74

[engnadeau]

Happy New Year @alex @hugovk @jdufresne !

What's the status of this PR?

[hugovk]

Looks good to me, but I don't think any of us three can merge.

[engnadeau]

Ahh! @sigmavirus24 is the merger :)

[gdubicki]

Python 2.6 tests are blocking #143 , which I care about. Can you please take a look at this MR, @sigmavirus24 ? Or otherwise perhaps share your permission with people who have more time for this project? Thanks in advance! :)

[perlpunk]

@gdubicki I believe tests for #143 were failing because of some travis + 2.6 issue. I just rebased my PR to master and force-pushed. 2.6 is passing now, waiting for 3.7-dev

[dstufft]

Also modern versions of pip can ignore versions of a library that don't work for a specific version of Python if said project sets metadata correctly. 2.6 users are going to increasingly run into issues where libraries don't work on 2.6 anymore (particularly since pip itself no longer supports it), and are likely going to want to upgrade to a version of pip with that mechanism just for their own sanity sake.

[cclauss]

Perfect timing... 20 days until Python 3.4 end of life.

print((date(2019, 3, 16) - date.today()).days, 'days until Python 3.4 end of life.')

https://devguide.python.org/index?#status-of-python-branches