Re: [Announcement] New Committer - Sam Skalicky

[Kshitij Kalambarkar]

Congrats Sam! Keep up the great work.

On Thu, 30 Jul, 2020, 8:49 AM Zhang Zhi,  wrote:

> Congrats Sam!!
>
> -Zhi
>
> On Wed, Jul 29, 2020 at 7:30 PM Chen, Ciyong 
> wrote:
>
> > Congratulations Sam!
> > Those are great features to MXNet.
> >
> > -Original Message-
> > From: Zhao, Patric 
> > Sent: Thursday, July 30, 2020 8:40 AM
> > To: dev@mxnet.incubator.apache.org
> > Subject: RE: [Announcement] New Committer - Sam Skalicky
> >
> > Congratulations, Sam, thanks all of your great works in MXNet 
> >
> > > -Original Message-
> > > From: Chaitanya Bapat 
> > > Sent: Thursday, July 30, 2020 1:12 AM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: [Announcement] New Committer - Sam Skalicky
> > >
> > > Congratulations Sam! Well deserved!
> > >
> > > On Wed, 29 Jul 2020 at 08:05, Marco de Abreu 
> > > wrote:
> > >
> > > > Welcome!
> > > >
> > > > -Marco
> > > >
> > > > On Wed, Jul 29, 2020, 4:58 PM sandeep krishnamurthy <
> > > > sandeep.krishn...@gmail.com> wrote:
> > > >
> > > > > Hello all,
> > > > >
> > > > > Please join me in welcoming Sam Skalicky(@samskalicky) as a new
> > > > > committer of Apache MXNet (incubating)!
> > > > >
> > > > > Sam has made a number of contributions to this project such as
> > > > > SubGraphs, Custom Ops, Accelerator APIs, along with several other
> > > > > operator implementations and bug fixes. Sam has been actively
> > > > > engaging in PR reviews, dev@ list discussions and helping the
> > > > > project and fellow contributors.
> > > > >
> > > > > Sam, thank you for all your contributions and looking forward to
> > > > > more support!
> > > > >
> > > > > Welcome, Sam!
> > > > >
> > > > > --
> > > > > Sandeep Krishnamurthy
> > > > >
> > > >
> > >
> > >
> > > --
> > > *Chaitanya Prakash Bapat*
> > > *+1 (973) 953-6299*
> > >
> > > [image: https://www.linkedin.com//in/chaibapat25]
> > > [image:
> > > https://www.facebook.com/chaibapat]
> > > [image:
> > > https://twitter.com/ChaiBapchya]  > >[image:
> > > https://www.linkedin.com//in/chaibapat25]
> > > 
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

[Kshitij Kalambarkar]

+ 1

* Built from source on Ubuntu 18.04 with CUDA, CUDNN
* Verified test_higher_order_grad.py

Great job!

On Wed, Jul 22, 2020 at 12:02 PM Chaitanya Bapat 
wrote:

> +1
>
> - Built from source on Ubuntu18 with CUDA ON, USE_INT64_TENSOR_SIZE ON
> - Verified large tensor tests work as expected on a p3.16xl instance [with
> 8 Tesla V100 GPUs]
> - Verified OpPerf utility works as expected.
>
> Steps followed:
> https://gist.github.com/ChaiBapchya/8a5131932693d4ca47281368c752b726
>
> Thanks Ciyong for leading with the releases. Incredible job.
>
> Regards,
> Chai
>
>
> On Tue, 21 Jul 2020 at 23:05, Karan Jariwala 
> wrote:
>
> > +1
> >
> > Build from source on Ubuntu 18 with CUDA/CUDNN/NCCL ON and verified with
> > Horovod 0.19.5 by running unittest and integration tests.
> >
> > Thanks,
> > Karan
> >
> > On Tue, Jul 21, 2020 at 10:23 PM Sheng Zha  wrote:
> >
> > > +1. I checked:
> > >
> > > [x] Are release files in correct location? Yes
> > > [x] Do release files have the word incubating in their name? Yes
> > > [x] Are the digital signature and hashes correct? Yes
> > > [x] Does DISCLAIMER file exist? Yes, DISCLAIMER-WIP
> > > [x] Do LICENSE and NOTICE files exists? Yes
> > > [x] Is the LICENSE and NOTICE text correct?
> > > Yes, though the license still reads "Copyright [] [name of
> copyright
> > > owner]", which needs correction.
> > >
> > > [x] Is the NOTICE year correct? Yes
> > > [x] Un-included software dependencies are not mentioned in LICENSE or
> > > NOTICE?
> > > No. mshadow is now contributed to MXNet via software grant and should
> be
> > > removed from NOTICE.
> > >
> > > [x] License information is not mentioned in NOTICE? Confirmed
> > >
> > > Is there any 3rd party code contained inside the release? If so:
> > > [x] Does the software have a compatible license? Yes. Minor issue:
> > > Dual license in cmake/Modules/FindJeMalloc.cmake.
> > >
> > > [x] Are all software licenses mentioned in LICENSE? Yes
> > > [x] Is the full text of the licenses (or pointers to it) in LICENSE?
> Yes
> > >
> > > Is any of this code Apache licensed? Do they have NOTICE files? If so:
> > > [x] Have relevant parts of those NOTICE files been added to this NOTICE
> > > file?
> > > No. TVM NOTICE file hasn't been included.
> > >
> > > [x] Do all source files have ASF headers?
> > > Yes, except those in 3rdparty folder and those mentioned in license.
> > > [x] Do the contents of the release match with what's tagged in version
> > > control? Yes
> > > [x] Are there any unexpected binary files in the release? No
> > > [x] Can you compile from source? Are the instruction clear? Yes,
> Makefile
> > > is present and is straightforward.
> > > Is the issue minor? Yes
> > > Could it possibly be fixed in the next release? Yes
> > >
> > > I vote with:
> > > [x] +1 release the software
> > >
> > >
> > > On 2020/07/20 17:25:50, "Skalicky, Sam" 
> > > wrote:
> > > > +1
> > > >
> > > > Tested:
> > > > - Make flow building from source, verified all example/extensions/*
> > work
> > > correctly
> > > > - staticbuild flow cpu & cu102 variants producing the pip wheels,
> > tested
> > > with custom extension library
> > > >
> > > > Sam
> > > >
> > > > On 7/20/20, 4:07 AM, "Chen, Ciyong"  wrote:
> > > >
> > > > CAUTION: This email originated from outside of the organization.
> Do
> > > not click links or open attachments unless you can confirm the sender
> and
> > > know the content is safe.
> > > >
> > > >
> > > >
> > > > Thanks Aston, Patric for the vote.
> > > >
> > > > Hi Community,
> > > >
> > > > I would like to call for action to test/validate/vote for the
> > > release candidate (1.7.0.rc1).
> > > > As we've not reached the quorum, I would like to extend the
> voting
> > > process to July 22, 23:59:59 PST.
> > > > Please prepare your time and provide feedback if you've tried
> with
> > > the pre-released code base, thanks!
> > > >
> > > > Best Regards,
> > > > Ciyong
> > > >
> > > > -Original Message-
> > > > From: Zhao, Patric 
> > > > Sent: Monday, July 20, 2020 11:36 AM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Cc: d...@mxnet.apache.org; Bob Paulin ; Henri
> > > Yandell ; Jason Dai ; Markus
> > > Weimer ; Michael Wall 
> > > > Subject: RE: [VOTE] Release Apache MXNet (incubating) version
> > > 1.7.0.rc1
> > > >
> > > > +1
> > > >
> > > > Passed the performance benchmarking for CPU tests and no
> regression
> > > is found.
> > > >
> > > >
> > > > > -Original Message-
> > > > > From: Aston Zhang 
> > > > > Sent: Sunday, July 19, 2020 1:45 PM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Cc: d...@mxnet.apache.org; Bob Paulin ; Henri
> > > Yandell
> > > > > ; Jason Dai ; Markus
> > > Weimer
> > > > > ; Michael Wall 
> > > > > Subject: Re: [VOTE] Release Apache MXNet (incubating) version
> > > > > 1.7.0.rc1
> > > > >
> > > > > +1
> > > > > Passed d2l-en v0.14.1:
> > > > > 

Re: [DISCUSS] Examples Repo for 2.0

[Kshitij Kalambarkar]

+1 Great Idea! It is quite useful to have working examples to refer to.

On Thu, Jul 16, 2020 at 12:17 PM Marco de Abreu 
wrote:

> +1 good idea!
>
> On Thu, Jul 16, 2020, 5:39 AM Skalicky, Sam 
> wrote:
>
> > +1 For regular testing, enhanced doc/tutorial
> >
> > > On Jul 15, 2020, at 7:40 PM, Sheng Zha  wrote:
> > >
> > > CAUTION: This email originated from outside of the organization. Do
> not
> > click links or open attachments unless you can confirm the sender and
> know
> > the content is safe.
> > >
> > >
> > >
> > > Hi,
> > >
> > > Over the years, MXNet accumulated many examples in the example folder
> > [1]. However, due to not testing them in the CI and in releases, many of
> > them are currently broken. I'd like to propose that we create a new
> > examples repo for MXNet 2.0 similar to how PyTorch hosts them [2].
> Further
> > more, the new examples repo should be evaluated periodically (e.g.
> weekly)
> > against the master branch to ensure that they are not broken.
> > >
> > > Thoughts and comments are welcome.
> > >
> > > Sheng
> > >
> > > [1] https://github.com/apache/incubator-mxnet/tree/master/example
> > > [2] https://github.com/pytorch/examples
> >
>

Re: MXNet Bot Demo

[Kshitij Kalambarkar]

Great Job. Would be really helpful.

Regards,
Kshiteej

On Wed, 25 Mar, 2020, 7:29 AM Chaitanya Bapat,  wrote:

> Yes Denisa, you can use it on existing PRs as well. Sorry for miswording.
>
> Bot will comment instructions on how-to-use for every new PR.
> You can invoke bot for all the PRs.
>
>
> On Tue, 24 Mar 2020 at 18:00, Denisa Roberts 
> wrote:
>
> > Hi- Only for new PRs? Can I use it for an existing PR to retrigger only
> > specific tests?
> >
> > On Tue, Mar 24, 2020 at 8:27 PM Chaitanya Bapat 
> > wrote:
> >
> >> Hello MXNet community,
> >>
> >> Update: Bot has been deployed  on apache/incubator-mxnet.
> >>
> >> For every new PR, bot will comment with a help message (instructing what
> >> command to comment)
> >> It can trigger all jobs or specific jobs for users.
> >>
> >> Do use and if you find issues/suggestions do comment on this mail thread
> >> or
> >> the GitHub issue :
> https://github.com/apache/incubator-mxnet/issues/17801
> >>
> >> Thanks to Denis, Sandeep, Joe, Pedro, Marco and the design doc reviewers
> >> for valuable feedback and guidance.
> >>
> >> Thank you,
> >> Chai
> >>
> >> On Mon, 23 Mar 2020 at 13:08, sandeep krishnamurthy <
> >> sandeep.krishn...@gmail.com> wrote:
> >>
> >> > Thank you Chaitanya and Marco for helping the MXNet community.
> >> >
> >> > On Mon, Mar 23, 2020 at 12:56 PM Marco de Abreu <
> >> marco.g.ab...@gmail.com>
> >> > wrote:
> >> >
> >> > > Sure, already done.
> >> > >
> >> > > -Marco
> >> > >
> >> > > On Mon, Mar 23, 2020 at 8:53 PM Chaitanya Bapat <
> chai.ba...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > Hello,
> >> > > > Update: Apache Infra Ticket for MXNet Bot
> >> > > > Thanks once again, Marco for opening the ticket. But turns out,
> >> Apache
> >> > > > Infra folks closed it stating: "Security concerns around allowing
> >> > unknown
> >> > > > person to submit PR and run our hardware". Furthermore, it goes
> onto
> >> > > state
> >> > > > that bot circumvents the dependence on Jenkins Admins which is
> like
> >> > > solving
> >> > > > a problem that doesn't exist.
> >> > > >
> >> > > > I sense there is some confusion in the communication (maybe on my
> >> > part).
> >> > > It
> >> > > > turns out the security concerns aren't actually correct.
> >> > > >
> >> > > > 1. Unknown person can submit a PR (before & after bot proposal),
> and
> >> > run
> >> > > > our hardware (pre as well as post bot).
> >> > > > 2. Code should be reviewed by somebody with an ICLA on file. This
> >> > doesn't
> >> > > > change either. Prior to merging a PR, code has to be approved by a
> >> > > > committer just like before.
> >> > > > Overall it looks like the job of the bot isn't clear to folks in
> >> Apache
> >> > > > Infra. Bot simply is a means for triggering CI (which could be
> done
> >> > > > manually by Log In to Jenkins -> PR -> Job -> Build) and doesn't
> >> quite
> >> > > > tweak with merging procedure. Yes, only addition is now unknown
> >> person
> >> > > (PR
> >> > > > Author) can trigger CI with a message (but that was possible
> anyway
> >> by
> >> > > > pushing a commit. Bot just prevents users from pushing empty
> commits
> >> > and
> >> > > > building entire suite).
> >> > > >
> >> > > > As can be seen from last 10 open PRs as of Monday 23rd March, 12pm
> >> PT
> >> > > most
> >> > > > PRs fail on 1/2 jobs. In such a scenario, the proposed MXNet bot
> >> would
> >> > > come
> >> > > > in handy for just invoking CI on that specific build (instead of a
> >> > > > non-committer PR Author to push empty commit : hurting on the
> >> resource,
> >> > > > time & cost considerations apart from undesirable dev experience)
> >> > > >
> >> > > > @Marco Since I am a non-committer, I guess these 2 clarifications
> >> need
> >> > to
> >> > > > be conveyed to the Apache Infra by someone with Committer access.
> >> > > >
> >> > > > What do you think?
> >> > > >
> >> > > > Thanks,
> >> > > > Chai
> >> > > >
> >> > > > On Sat, 21 Mar 2020 at 16:08, Marco de Abreu <
> >> marco.g.ab...@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > >
> >> > > > > the ticket has been created:
> >> > > > > https://issues.apache.org/jira/browse/INFRA-20005
> >> > > > >
> >> > > > > Best regards,
> >> > > > > Marco
> >> > > > >
> >> > > > > On Thu, Mar 19, 2020 at 11:49 PM Marco de Abreu <
> >> > > marco.g.ab...@gmail.com
> >> > > > >
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Sounds like a good plan!
> >> > > > > >
> >> > > > > > Please send me the URL (please make sure it's backed by DNS
> and
> >> not
> >> > > > just
> >> > > > > > the gateway URL) of the webhook handler, GitHub events you're
> >> > > > interested
> >> > > > > in
> >> > > > > > and the shared secret in a private email to my personal email
> >> > > address.
> >> > > > I
> >> > > > > > will then create the ticket with Apache infra.
> >> > > > > >
> >> > > > > > -Marco
> >> > > > > >
> >> > > > > > Chaitanya Bapat  schrieb am Do., 19.
> März
> >> > > 2020,
> >> > > > > > 23:07:
> >> > > 

Re: [Announcement] New Committer - Anirudh Acharya

[Kshitij Kalambarkar]

Congrats Anirudh!

On Sun, Sep 29, 2019, 11:13 Sheng Zha  wrote:

> Congrats! Now Anirudh is officially the most popular name among the MXNet
> committers :P
>
> -sz
>
> On 2019/09/27 22:57:22, Furkan KAMACI  wrote:
> > Hi,
> >
> > Congrats Anirudh!
> >
> > Kind Regards,
> > Furkan KAMCI
> >
> > 28 Eyl 2019 Cmt, saat 01:34 tarihinde Marco de Abreu <
> > marco.g.ab...@gmail.com> şunu yazdı:
> >
> > > Welcome!
> > >
> > >
> > > On Sat, Sep 28, 2019 at 12:06 AM Chaitanya Bapat  >
> > > wrote:
> > >
> > > > Congratulations Anirudh! Well deserved!
> > > >
> > > > On Thu, 26 Sep 2019 at 10:10, Chris Olivier 
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > Please join me in welcoming Anirudh Acharya as a new committer of
> > > Apache
> > > > > MXNet (incubating)!
> > > > >
> > > > > Anirudh Acharya has been contributing to the MXNet project for a
> year
> > > and
> > > > > half now and has made several improvements to the MXNet R project
> and
> > > > > continues to contribute by adding optimizers, fixing tests and
> actively
> > > > > providing feedback on the PRs and has good understanding of
> building
> > > > > operators in MXNet and architecture in general.
> > > > >
> > > > > Welcome, Anirudh!
> > > > >
> > > >
> > > >
> > > > --
> > > > *Chaitanya Prakash Bapat*
> > > > *+1 (973) 953-6299*
> > > >
> > > > [image: https://www.linkedin.com//in/chaibapat25]
> > > > [image:
> > > https://www.facebook.com/chaibapat
> > > > ]
> > > > [image:
> > > > https://twitter.com/ChaiBapchya]  > > >[image:
> > > > https://www.linkedin.com//in/chaibapat25]
> > > > 
> > > >
> > >
> >
>

Re: [Announcement] New Committer - Junru Shao

[Kshitij Kalambarkar]

Congratulations!!

On Sun, Sep 8, 2019, 14:51 Marco de Abreu  wrote:

> Congratulations!
>
> -Marco
>
> MiraiWK WKCN  schrieb am So., 8. Sep. 2019, 06:10:
>
> > Congrats, Junru!
> > 
> > 发件人: Sheng Zha 
> > 发送时间: 2019年9月8日 11:14
> > 收件人: d...@mxnet.apache.org 
> > 主题: [Announcement] New Committer - Junru Shao
> >
> > Hi all,
> >
> > Please join me in welcoming Junru Shao as a new committer of Apache MXNet
> > (incubating)!
> >
> > Junru made a number of contributions to this project such as cond and
> > while_loop control-flow
> > operators, enabling dynamic shape in control-flow ops, and zero-copy
> array
> > creation from numpy
> > array. He's also been actively working on numpy-compatible programming
> > experience and
> > has helped the community recently by driving the 1.4.1 patch release.
> >
> > Welcome, Junru!
> >
> > -sz
> >
>

Re: [Announcement] New Committer - Lai Wei

[Kshitij Kalambarkar]

Congratulations Lai!

On Sun, Aug 4, 2019, 09:29 Zhao, Patric  wrote:

> Congratulation, Lai.
>
> Well done for the very challenge release 1.5 and you make the progress
> going smoothly 
>
>
> > -Original Message-
> > From: kellen sunderland 
> > Sent: Sunday, August 4, 2019 9:32 AM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: [Announcement] New Committer - Lai Wei
> >
> > Congrats Lai.  Well deserved.
> >
> > On Sat, Aug 3, 2019, 6:18 PM Jake Lee  wrote:
> >
> > > Congratulations! Lai
> > >
> > > On Sat, Aug 3, 2019 at 6:13 PM Sheng Zha  wrote:
> > >
> > > > Hi all,
> > > >
> > > > Please join me in welcoming Lai (Roy) Wei as a new committer of
> > > > Apache MXNet (incubating)!
> > > >
> > > > Lai was one of the main contributor to the MXNet Keras frontend.
> > > > More recently, he contributed the Gluon estimator API, which enables
> > > > easy usage and better modularization for the training scripts of
> > > > Gluon. He also persisted and helped driving the long-running 1.5.0
> > > > release process.
> > > >
> > > > Welcome, Lai!
> > > >
> > > > -sz
> > > >
> > > >
> > >
>

Re: [Discuss] MXNet Python 2 Support Deprecation

[Kshitij Kalambarkar]

+1

On Fri, Jul 19, 2019, 04:28 Pedro Larroy 
wrote:

> Seems 3.6 is a reasonable choice.
>
> On Thu, Jul 18, 2019 at 2:15 PM Marco de Abreu 
> wrote:
> >
> > Looking at EOL is certainly a good idea! I think once we get closer to
> > deprecation, we can check adoption statistics to make a well-informed
> > decision that gives us the most advantages without dropping the ball on a
> > majority of users (or supporting a branch that is going EOL soon). A
> survey
> > from 2018 [1] determined the following distribution:
> > 3.5: 11%
> > 3.6: 54%
> > 3.7: 30%
> >
> > Deprecation for 3.5 is scheduled for 2020-09-13 [2]. Deprecation for 3.6
> is
> > scheduled for 2021-12-23 [2].Deprecation for 3.7 is scheduled
> > for 2023-06-27 [2].
> >
> > Following the trend, I'd say that it would be a decision between Python
> 3.6
> > and 3.7. Later on, I'd propose to check recent surveys and also have a
> > separate thread to determine if there's anything we're missing (e.g. a
> big
> > company being unable to use Python 3.7). What do you think?
> >
> > Best regards,
> > Marco
> >
> > [1]: https://www.jetbrains.com/research/python-developers-survey-2018/
> > [2]: https://devguide.python.org/#status-of-python-branches
> >
> > On Thu, Jul 18, 2019 at 9:42 PM Yuan Tang 
> wrote:
> >
> > > I would suggest supporting Python 3.5+ since the earlier versions have
> > > reached end-of-life status:
> > > https://devguide.python.org/devcycle/#end-of-life-branches
> > >
> > > On Thu, Jul 18, 2019 at 3:36 PM Pedro Larroy <
> pedro.larroy.li...@gmail.com
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > This would simplify CI, reduce costs and more. I think a followup
> > > > question is what would be the mininum Python3 version supported?
> > > > Depending on that we might be able to use type annotations for
> example
> > > > or other features.
> > > >
> > > > Pedro.
> > > >
> > > > On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang 
> > > > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu 
> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He 
> > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Best regards,
> > > > > > >
> > > > > > > Tong He
> > > > > > >
> > > > > > >
> > > > > > > Jake Lee  于2019年7月18日周四 上午11:29写道：
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao <
> > > > junrushao1...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya <
> > > > > > > anirudhk...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu <
> > > > > > > > marco.g.ab...@gmail.com
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > +1
> > > > > > > > > > >
> > > > > > > > > > > -Marco
> > > > > > > > > > >
> > > > > > > > > > > Sheng Zha  schrieb am Do., 18.
> Juli
> > > > 2019,
> > > > > > > > 19:59:
> > > > > > > > > > >
> > > > > > > > > > > > Dear MXNet community,
> > > > > > > > > > > >
> > > > > > > > > > > > I'd like to reopen the discussion on deprecating
> python2
> > > > > > support.
> > > > > > > > > This
> > > > > > > > > > > > would help modernize the design and engineering
> practice
> > > in
> > > > > > MXNet
> > > > > > > > to
> > > > > > > > > > help
> > > > > > > > > > > > improve speed and quality.
> > > > > > > > > > > >
> > > > > > > > > > > > For this purpose, I reopened the issue on this here:
> > > > > > > > > > > >
> https://github.com/apache/incubator-mxnet/issues/8703
> > > > > > > > > > > >
> > > > > > > > > > > > If the consensus is towards the direction of dropping
> > > > python2
> > > > > > > > > support,
> > > > > > > > > > I
> > > > > > > > > > > > suggest we announce our plan to drop python2 support
> in
> > > the
> > > > > > next
> > > > > > > > > > release,
> > > > > > > > > > > > and actually drop the support in the next major
> version.
> > > > > > Thanks.
> > > > > > > > > > > >
> > > > > > > > > > > > -sz
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Yuxi(Darren) Hu, Ph.D.
> > > > > > Software Development Engineer
> > > > > > Amazon Web Services
> > > > > >
> > > >
> > >
>

Slack Invitation

[Kshitij Kalambarkar]