Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1587
I prefer to use `%livy.pyspark` & `$livy.pyspark3` instead of
`zeppelin.livy.kind`. Because if user change `zeppelin.livy.kind` some
paragraphs may not work again, this is very confusing. So explicitly specifying
python version is better IMO. And could you wait for #1612 which is
refactoring livy interpreter ? After #1612 , it should be pretty easy to add
`%livy.pyspark3`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
