Python 3.4 No Longer Supported due to Colorama Dependency

[mlammers86]

I don't use tox directly, or even close to indirectly, but a lot of packages that I depend on (awscli, for example) do. I also know that I shouldn't be using Python 3.4, but some of the software I maintain unfortunately does. On December 6, the package "colorama" dropped support for Python 3.4, and my new deploys are failing because of this. This package (tox) uses colorama >= 0.4.1 in setup.cfg, and because colorama 0.4.3 no longer supports Python 3.4, neither does anything else dependent on it.

Now, I might be totally wrong on all of this, but this is the only thing I can come up with as a reason why colorama is being installed from my requirements.txt file. Regardless, can you either change it to colorama == 0.4.1 in setup.cfg, or do something else to continue maintaining support for Python 3.4 for the time being? Thanks!

[gaborbernat]

Feel free to open a pr where you set it to greater or equal to 0.4.1 🤔

[ssbarnea]

To be honest I would prefer dropping support for py34 in tox.

[asottile]

@mlammers86 sounds like you're using a too-old version of pip? can you try using something newer (I think you need pip 9.0.1+)?

[jugmac00]

Python 3.4 is no longer officially supported by tox.

I guess this issue could be closed then?

[mlammers86]

Yes, I believe so.

On Mon, Nov 9, 2020 at 2:28 AM Jürgen Gmach ***@***.***> wrote: Python 3.4 is no longer officially supported by tox. I guess this issue could be closed then? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1483 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABO6SBEYWV2RQJDRCR4ESETSO6KX7ANCNFSM4JYLLFVQ> .

-- Matt Lammers mlammers08atmos@gmail.com (Formerly matt.lammers@utah.edu) (801) 440-1730