From srinavya.d at gmail.com Thu May 9 06:25:04 2019 From: srinavya.d at gmail.com (Navya Dommeti) Date: Thu, 9 May 2019 15:55:04 +0530 Subject: [Python-porting] Regarding 2to3 tool Message-ID: Hi, I'm totally confused on how to port to python 3. Our codebase has no enough test suite. Can you please help me what to in addition after porting code to python 3 using 2to3 tool. If possible, please provide it as a checklist. Will be very grateful to you, TIA! -- Regards, Navya Dommeti -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcarans at yahoo.co.uk Tue May 14 10:39:36 2019 From: mcarans at yahoo.co.uk (Michael Rans) Date: Tue, 14 May 2019 14:39:36 +0000 (UTC) Subject: [Python-porting] Regarding 2to3 tool In-Reply-To: References: Message-ID: <1716207813.565790.1557844776501@mail.yahoo.com> Hi Navya, This might not be the news you want to hear, but the first thing on the checklist would probably be to ensure your tests cover as much of the codebase as possible. Cheers,Mike On Tuesday, 14 May 2019, 16:34:00 CEST, Navya Dommeti wrote: Hi, I'm totally confused on how to port to python 3.?Our codebase has no enough test suite. Can you please help me what to in addition after porting code to python 3 using 2to3 tool. If possible, please provide it as a checklist. Will be very grateful to you, TIA! -- Regards,Navya Dommeti_______________________________________________ Python-porting mailing list Python-porting at python.org https://mail.python.org/mailman/listinfo/python-porting -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcannon at gmail.com Tue May 14 14:11:38 2019 From: bcannon at gmail.com (Brett Cannon) Date: Tue, 14 May 2019 11:11:38 -0700 Subject: [Python-porting] Regarding 2to3 tool In-Reply-To: <1716207813.565790.1557844776501@mail.yahoo.com> References: <1716207813.565790.1557844776501@mail.yahoo.com> Message-ID: https://docs.python.org/3/howto/pyporting.html had an outline and having good tests is step 2. On Tue., May 14, 2019, 07:40 Michael Rans via Python-porting, < python-porting at python.org> wrote: > Hi Navya, > > This might not be the news you want to hear, but the first thing on the > checklist would probably be to ensure your tests cover as much of the > codebase as possible. > > Cheers, > Mike > > On Tuesday, 14 May 2019, 16:34:00 CEST, Navya Dommeti < > srinavya.d at gmail.com> wrote: > > > Hi, > > I'm totally confused on how to port to python 3. > Our codebase has no enough test suite. > > Can you please help me what to in addition after porting code to python 3 > using 2to3 tool. > > If possible, please provide it as a checklist. > > Will be very grateful to you, > > TIA! > > -- > Regards, > Navya Dommeti > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > -------------- next part -------------- An HTML attachment was scrubbed... URL: From patelkhelan11 at gmail.com Tue May 14 10:44:12 2019 From: patelkhelan11 at gmail.com (khelan patel) Date: Tue, 14 May 2019 10:44:12 -0400 Subject: [Python-porting] Python 2to3 automated CI/CD plugin for code scan Message-ID: Hi Team, Hope this email finds y'all well. We are starting our efforts to move code repo from python2 to python3. Can someone help if they have setup Travis/Jenkins or any other plugin that would scan Python2 code and help with the potential code paths that would break for python3 (code scan)? In general, looking for automated code scan (based out of git repo). Would appreciate any help/suggestion/guidance. Thanks in advance! -- Thanks & Regards, Khelan Patel -------------- next part -------------- An HTML attachment was scrubbed... URL: From justinisrael at gmail.com Tue May 14 15:52:00 2019 From: justinisrael at gmail.com (Justin Israel) Date: Wed, 15 May 2019 07:52:00 +1200 Subject: [Python-porting] Regarding 2to3 tool In-Reply-To: References: Message-ID: On Wed, May 15, 2019, 4:03 AM < > From: Navya Dommeti > To: python-porting at python.org > Cc: > Bcc: > Date: Thu, 9 May 2019 15:55:04 +0530 > Subject: [Python-porting] Regarding 2to3 tool > Hi, > > I'm totally confused on how to port to python 3. > Our codebase has no enough test suite. > > Can you please help me what to in addition after porting code to python 3 > using 2to3 tool. > > If possible, please provide it as a checklist. > > Will be very grateful to you, > > TIA! > > -- > Regards, > Navya Dommeti > > > > ---------- Forwarded message ---------- > From: Michael Rans > To: python-porting at python.org, Navya Dommeti > Cc: > Bcc: > Date: Tue, 14 May 2019 14:39:36 +0000 (UTC) > Subject: Re: [Python-porting] Regarding 2to3 tool > Hi Navya, > > This might not be the news you want to hear, but the first thing on the > checklist would probably be to ensure your tests cover as much of the > codebase as possible. > > Cheers, > Mike > In my limited experience thus far, aside from needing the test coverage, I have found the Python Future documentation to be all the "checklist" that I need: https://python-future.org/quickstart.html > On Tuesday, 14 May 2019, 16:34:00 CEST, Navya Dommeti < > srinavya.d at gmail.com> wrote: > > > Hi, > > I'm totally confused on how to port to python 3. > Our codebase has no enough test suite. > > Can you please help me what to in addition after porting code to python 3 > using 2to3 tool. > > If possible, please provide it as a checklist. > > Will be very grateful to you, > > TIA! > > -- > Regards, > Navya Dommeti > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brett at python.org Sat May 25 13:01:42 2019 From: brett at python.org (Brett Cannon) Date: Sat, 25 May 2019 10:01:42 -0700 Subject: [Python-porting] Python 2to3 automated CI/CD plugin for code scan In-Reply-To: References: Message-ID: Pylint at least had some checks you could flip on to make sure you don't regress. On Sat., May 25, 2019, 06:12 khelan patel, wrote: > Hi Team, > > Hope this email finds y'all well. > > We are starting our efforts to move code repo from python2 to python3. Can > someone help if they have setup Travis/Jenkins or any other plugin that > would scan Python2 code and help with the potential code paths that would > break for python3 (code scan)? > > In general, looking for automated code scan (based out of git repo). > > Would appreciate any help/suggestion/guidance. Thanks in advance! > -- > Thanks & Regards, > Khelan Patel > > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > -------------- next part -------------- An HTML attachment was scrubbed... URL: