Dear Murray The packaged Jupyter Notebook environments are made available, to provide people who are interested in the J / Jupyter Notebook - Integration an easy (batteries included) way to test it without cluttering their existing Jupyter environments.
So I think yes, there is really a need for these packages. I can confirm that J806 beta works with the existing jkernel. Chris has successfully tested it on a Mac, and I have tested it on Windows. So it seems that it's not an issue with jkernel and J806 beta. The more complex way, to install the jkernel into an existing Jupyter environment is, of course, still available. But yes, I know, it's not that easy as using the pre-configured environments. My problem is that I cannot reproduce (at least at the moment) your issues with J806 beta and jkernel. I will give it another shot, next weekend. Best Regards Martin > Message: 1 > Date: Tue, 9 May 2017 10:32:23 -0400 > From: Murray Eisenberg <[email protected]> > To: [email protected] > Subject: Re: [Jgeneral] General Digest, Vol 139, Issue 7 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > I don’t understand the need for this new packaged system, which still uses > J905, given that I > was easily able to make the Anaconda-based Jupyter work > with the existing J805 installation via jkernel — once I changed my path so > the Anaconda python was first. > > —> My remaining issue, as I reported, is that jkernel (and Anaconda jupyter > and python) does not work with J806 (six). > > Why would I want to have to maintain a whole separate J installation > directory? > > Os is this just to test a concept of bundling everything — with the goal of > making the jupyter IDE a standard part of the J distribution? > > Murray. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
