Re: [EXTERNAL] Re: Python2 EoL

["Gray, Jonathan" <Jo...@comcast.com>]

I'm not a fan of pypi because it will add another step to our release process to manage with an external source to maintain.  If we want to deprecate the 2.x client ahead of the EOL date in the 4.0 release, that's fine with me since it can be versioned where it is today I think.

Jonathan G

On 11/1/18, 9:04 AM, "Dave Neuman" <ne...@apache.org> wrote:

    I am not sure if Apache is cool with us putting the client on PyPi, so that
    is something we should look into (are other Apache projects there?).
    I don't really have an opinion on moving from 2 - 3, so if that is
    something you want to do, go for it.
    
    On Tue, Oct 30, 2018 at 8:31 AM Fieck, Brennan <Br...@comcast.com>
    wrote:
    
    > Currently our Python client is primarily built for Python2 (though with a
    > PR I have pending to fix one little thing it works with up to v3.6), but
    > Python 2 will be totally dead in 1 year, 2 months, 1 day, 14 hours and
    > approx. 34 minutes as of the time of this writing.
    >
    > After that date, it will no longer be reasonable to support Python2. I
    > propose pushing a release of the client to PyPi (the name 'trafficcontrol'
    > is free) so that it can be hosted in a Python2-compatible state while
    > continuing to develop only for Python3. People will be able to install and
    > use the client with Python2, but updates for that version will halt when we
    > drop Python2 support.
    >
    > I'd also like to know if there's any interest in dropping Python2 support
    > for the Traffic Control 4.0 release, even if that happens before 2020 -
    > because a major revision is probably the best time to make a breaking
    > change like that.
    >