Skip to content

ZEPPELIN-1325: WIP - Python, advanced interpreter impl - #1495

Closed
bzz wants to merge 7 commits into
apache:masterfrom
bzz:python/advanced-interpreter
Closed

ZEPPELIN-1325: WIP - Python, advanced interpreter impl#1495
bzz wants to merge 7 commits into
apache:masterfrom
bzz:python/advanced-interpreter

Conversation

@bzz

@bzzbzz commented Oct 7, 2016

Copy link
Copy Markdown
Member

What is this PR for?

This is different implementation of Python interpreter that communicates to external Python 2/3 process (not just REPL) though RPC.

It aims for rich feature set, missing in current implementation:

  • better error handling
  • PEP-8 syntax compatibility
  • code-completion
  • job progress/cancellation.
  • windows support

screen shot 2016-10-07 at 13 17 13

What type of PR is it?

Improvement

TODOs

  • Initial PoC
  • add %python2.dep interpreter impl
  • install default python dependencies automatically
  • update grpc version to 1.0 to make it python3 compatible
  • make sure it works on windows
  • change ambiguous name/package python2 to something better, like python-remote or python-rich or something else
  • update bin_licenses/LICENSE

What is the Jira issue?

ZEPPELIN-1325

How should this be tested?

Bind Python2 (name will be changed) interpreter and run any python code i.e ZEPPELIN-1133

Questions:

  • Does the licenses files need update? Yes
  • Is there breaking changes for older versions? No
  • Does this needs documentation? May be

@zjffdu

zjffdu commented Jan 25, 2017

Copy link
Copy Markdown
Contributor

@bzz What the status of this PR ? Do you plan to put it in 0.8 ? Because I think python become more popular with the boom of data science and deep learning, so it would be better to for zeppelin improve the python interpreter.

@zjffdu

Copy link
Copy Markdown
Contributor

ping @bzz Any updates ?

@zjffduzjffdu mentioned this pull request Mar 7, 2017
@asfgitasfgit closed this in c38a0a0May 9, 2018
asfgit pushed a commit that referenced this pull request May 9, 2018
close#83close#86close#125close#133close#139close#146close#193close#203close#246close#262close#264close#273close#291close#299close#320close#347close#389close#413close#423close#543close#560close#658close#670close#728close#765close#777close#782close#783close#812close#822close#841close#843close#878close#884close#918close#989close#1076close#1135close#1187close#1231close#1304close#1316close#1361close#1385close#1390close#1414close#1422close#1425close#1447close#1458close#1466close#1485close#1492close#1495close#1497close#1536close#1545close#1561close#1577close#1600close#1603close#1678close#1695close#1739close#1748close#1765close#1767close#1776close#1783close#1799
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@bzz@zjffdu