Also, it has been reported that pip wheel installation with latest pip version 20.0.1 breaks installation of MXNet pip wheels which have py2.py3 in the wheel name. This breaks all existing released versions. Work around is to install the older version of pip "pip install pip==19.3.1”.
Sam > On Jan 21, 2020, at 4:35 PM, Chung, Alex <alch...@amazon.com.INVALID> wrote: > > +1 > > Sincerely, > > Alex Chung > Senior Product Manager | AWS AI > > ________________________________________ > From: shiwen hu <yajiedes...@gmail.com> > Sent: Tuesday, January 21, 2020 4:26 PM > To: dev@mxnet.incubator.apache.org > Subject: Re: MXNet 1.6 as last release with Python 2 support? > > +1 > > Lai Wei <roywei...@gmail.com> 于2020年1月18日周六 上午2:51写道： > >> +1 >> >> >> Best Regards >> >> Lai >> >> >> On Fri, Jan 17, 2020 at 10:39 AM Lin Yuan <apefor...@gmail.com> wrote: >> >>> +1 >>> >>> On Fri, Jan 17, 2020 at 10:04 AM Xingjian SHI <xsh...@connect.ust.hk> >>> wrote: >>> >>>> +1. We should move to support Python>=3.5 only. >>>> >>>> Get Outlook for iOS<https://aka.ms/o0ukef> >>>> ________________________________ >>>> From: Lausen, Leonard <lau...@amazon.com.INVALID> >>>> Sent: Friday, January 17, 2020 10:02:30 AM >>>> To: d...@mxnet.apache.org <d...@mxnet.apache.org> >>>> Subject: Re: MXNet 1.6 as last release with Python 2 support? >>>> >>>> If the lazy consensus passes, I believe the minimum Python version >>>> supported >>>> would be Python 3.5. >>>> >>>> Python 3.5 because it seems to be the minimum Python 3 version tested >> by >>>> our CI, >>>> specifically in the jobs running on Ubuntu 16.04. >>>> >>>> Best regards >>>> Leonard >>>> >>>> On Fri, 2020-01-17 at 17:36 +0000, Lausen, Leonard wrote: >>>>> Dear MXNet community, >>>>> >>>>> as effective January 1, 2020, no new bug reports, fixes, or changes >>> will >>>> be >>>>> made >>>>> to Python 2, and as MXNet 1.6 will be released after January 1, >> 2020, I >>>>> suggest >>>>> to announce in the MXNet 1.6 release notes that MXNet 1.6 is the last >>>> release >>>>> supporting Python 2. >>>>> >>>>> We have previously reached consensus on announcing that Python 2 is >>>> dropped in >>>>> the next major release (ie. MXNet 2), however, given the delay in 1.6 >>>> release, >>>>> the plan to release 1.7 in the future and that Python 2 is dead >>> already I >>>>> think >>>>> we can revisit this assumption. >>>>> >>>>> Advantages are >>>>> - Time savings for developers, as Python 3 standard library contains >>> more >>>>> features than Python 2, and it is more efficient to target only 1 >>>> language >>>>> (Python 3) instead of 2 languages (Python 2 & 3) >>>>> - Simplification and cost savings for CI >>>>> >>>>> I thus suggest 72h lazy consensus for announcing dropping of Python 2 >>> as >>>>> described above. If you disagree, please veto (send "-1") and we can >>>> continue >>>>> supporting Python 2 in all 1.x releases as per previous consensus. >> Note >>>> that >>>>> at >>>>> the time of previous consensus, no 1.7 release was planned. >>>>> >>>>> Best regards >>>>> Leonard >>>> >>> >>
