Support legacy Python 2.6/3.3/3.4 for python-future

Describe the bug

We are thinking of porting https://github.com/PythonCharmers/python-future from Travis to Github Action, however we noticed python2.6 was not listed in: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json

Which version of the action are you using?

• v1
• v2

Environment

• self-hosted
• Linux
• Windows
• Mac

Python Versions

2.6.X

Run/Repo Url https://github.com/sfdye/python26-test https://github.com/sfdye/python26-test/runs/769263785?check_suite_focus=true

Additional context

I understand python2.6 is already EOL long time ago, but future is compatible layer to ease the migration from Python 2 to Python 3, so the use case still makes sense.

[konradpabjan]

Hey @sfdye

Since it’s not working we’ll go ahead and remove the extra distributions of Python that we added.

I thought this would be a quick compile + publish but there appears to be a host of other problems 😟 Given that these distributions are so old and we haven’t seen any other customers asking for this, we won’t be officially supporting them.

[konradpabjan]

Hi @sfdye

We’ve published Python 2.6.9 to actions/python-versions: https://github.com/actions/python-versions/blob/1cb5ff2fb053a5513ba297d229ab9737b10efba3/versions-manifest.json#L829

We were going to not support this as 2.6.9 is very very old however we quickly tried compiling it with our existing scripts and it worked (exit code 0). Some tests however did fail (some modules failed to build) but we figured we can publish it anyway as it might work and the certain modules might just be an issue with our tests.

A word of caution though that I have no idea if everything is working correctly and there will be no support if certain things aren’t working correctly. If it ends up being totally busted then we can remove it from python-versions, but it’s worth at least trying since it compiled successfully.