+1 This would simplify usage, and remove a large class of python questions and confusion on our mailing list. Several users assume that our R and Python featureset has parity with the primary kernels.
On Tue, 25 Sep 2018 at 12:46 kbat...@gmail.com <kbat...@gmail.com> wrote: > +1 > The benefits that Luciano points out far outweigh the, probably > seldom-used, context sharing capabilities with limited features, IMHO. > This will eliminate an entire class of issues and questions while allowing > contributors to narrow their focus only on scala functionality and > improvements. > > On 2018/09/25 16:04:33, Luciano Resende <luckbr1...@gmail.com> wrote: > > Toree currently has some support for Python and R which are a thin > > wrapper around what is provided in Spark. While this enables sharing > > the Spark session and SQL Context between Scala and Python code, it > > brings a huge gap on functionality when comparing with other Python > > kernels like IPython and IRKernel. Adding to that, there is no > > community member that is actively enhancing and contributing to these > > two areas. > > > > Based on these, I would like to suggest the following to be done for > > Toree 0.3.0 release timeframe: > > - Remove Python and R support from Toree > > - Document possible suggestions on Toree website (e.g. IPython, > > IRKernel or others more active on their respective community) > > > > Some of the benefits: > > - Avoid user confusion and frustration > > - Improve kernel startup performance > > - Cleaner code to maintain > > > > Please let me know your thoughts. > > > > [1] > https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > > > -- regards Marius van Niekerk
