RE: [EXTERNAL] Re: Python 2 to Python 3.7+

2021-04-20 Thread Shanyu Zhao
Thanks JB,

I wonder why we have version limit for pip and setuptools in .travis.yml:
- sudo pip2 -q install --upgrade "pip < 10.0.0" "setuptools < 36"

It is causing problem described in:
https://issues.apache.org/jira/browse/LIVY-853

Thanks,
Shanyu

-Original Message-
From: Jean-Baptiste Onofre  
Sent: Wednesday, March 31, 2021 10:32 PM
To: dev@livy.apache.org
Cc: d...@livy.incubator.apache.org
Subject: [EXTERNAL] Re: Python 2 to Python 3.7+

Hi Renat,

I think it makes sense to upgrade to Python 3, and I will bump Livy to a new 
major version (just to be clear for users).

I propose to bump to version 1.0.0-incubating-SNAPSHOT including:
- Python 3 update
- Spark 3 update
- other important updates (I already have some branches ready)

If no objection, I will create a 0.x branch with current 0.8.0-incubating to 
just keep the current state.

Regards
JB

> Le 1 avr. 2021 à 06:42, Renat Bekbolatov  a 
> écrit :
> 
> Hello!
> 
> First of all, thank you all for making this project possible.
> 
> Livy is adopted by many organizations and has been incredibly useful. 
> It is also what made Jupyter notebooks work with Spark, via 
> sparkmagic, which by itself already made a huge impact in the world of 
> Data Science and Machine Learning, Data Engineering with Spark.
> 
> We are thinking of making some updates to Apache Livy and noticed that 
> it relies on Python 2.
> 
> As we all know, PSF decided to sunset Python 2 as of January last 
> year, with no further support - including security patches - available 
> anymore.
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> python.org%2Fdoc%2Fsunset-python-2%2Fdata=04%7C01%7Cshzhao%40micr
> osoft.com%7C164318c5e1f0412dbb4508d8f4cf7338%7C72f988bf86f141af91ab2d7
> cd011db47%7C1%7C0%7C637528519125022452%7CUnknown%7CTWFpbGZsb3d8eyJWIjo
> iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
> ;sdata=VMdoOMWyJTq1y%2BLSRIuwLH0npyMYGo9bQT7LCAfGJJw%3Dreserved=0
> 
> According to JetBrains' Python Developers Survey 2018, already in 2018 
> Python 2 usage by developers was at 16% and was dropping rapidly.
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> jetbrains.com%2Fresearch%2Fpython-developers-survey-2017%2Fdata=0
> 4%7C01%7Cshzhao%40microsoft.com%7C164318c5e1f0412dbb4508d8f4cf7338%7C7
> 2f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637528519125032454%7CUnknown
> %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
> XVCI6Mn0%3D%7C1000sdata=lyZLoGq2l2yhOBSjERi3wT9vZOMqgeCE0q0Izv0Rw
> R8%3Dreserved=0
> 
> Are there any plans to drop support for Python 2 and move to Python 3.7+?
> How hard in your estimate would it be to make this upgrade?
> 
> Kind regards,
> Renat
> 



Re: Python 2 to Python 3.7+

2021-03-31 Thread Jean-Baptiste Onofre
Hi Renat,

I think it makes sense to upgrade to Python 3, and I will bump Livy to a new 
major version (just to be clear for users).

I propose to bump to version 1.0.0-incubating-SNAPSHOT including:
- Python 3 update
- Spark 3 update
- other important updates (I already have some branches ready)

If no objection, I will create a 0.x branch with current 0.8.0-incubating to 
just keep the current state.

Regards
JB

> Le 1 avr. 2021 à 06:42, Renat Bekbolatov  a 
> écrit :
> 
> Hello!
> 
> First of all, thank you all for making this project possible.
> 
> Livy is adopted by many organizations and has been incredibly useful. It is 
> also
> what made Jupyter notebooks work with Spark, via sparkmagic, which by itself
> already made a huge impact in the world of Data Science and Machine Learning, 
> Data Engineering with Spark.
> 
> We are thinking of making some updates to Apache Livy and noticed that it
> relies on Python 2.
> 
> As we all know, PSF decided to sunset Python 2 as of January last year, with 
> no 
> further support - including security patches - available anymore.
> https://www.python.org/doc/sunset-python-2/
> 
> According to JetBrains' Python Developers Survey 2018, already in 2018 Python 
> 2
> usage by developers was at 16% and was dropping rapidly.
> https://www.jetbrains.com/research/python-developers-survey-2017/
> 
> Are there any plans to drop support for Python 2 and move to Python 3.7+?
> How hard in your estimate would it be to make this upgrade?
> 
> Kind regards,
> Renat
>