Dear Darcy, Miguel Thanks to both for the suggestions. I agree with Darcy that we could develop the plugin outside the main svn tree. And for the moment I have no clear ideas about ensuring the proper runtime environment, some experimentation with the solutions Miguel described is needed.
Anyway I really think that it is not difficult to modify jupyter_console to output TeXmacs’s plugin protocol. I will look at this as soon as I have some time. As for Guile 2.0, at the moment I’m trying to look at the remaining bugs which are a bit subtle since they are generated by the different evaluation strategy wrt 1.8. Best Max > On 13. Jun 2019, at 16:56, Darcy Shen <sad...@zoho.com> wrote: > > I suggest we should develop the jupyter plugin independently. I mean, we > should not code under the SVN repo. It is not a good idea to package python > binary and dependencies in TeXmacs. > > Just like https://github.com/texmacs/TeXmacs.scala > <https://github.com/texmacs/TeXmacs.scala> , simply start it as a github repo. > > And for now, I do think we should focus on upgrading guile to 2.x for GNU > TeXmacs. Once we migrate to guile 2.x, we can make TeXmacs available in > Debian/Ubuntu/... > > Personally, this is my dev plan: > http://forum.texmacs.cn/t/my-development-in-2019-on-gnu-texmacs-sadhen/37 > <http://forum.texmacs.cn/t/my-development-in-2019-on-gnu-texmacs-sadhen/37> > > However, I'd like to help if anyone starts to write a jupyter plugin. And I > do think the plugin system should be improved. > > > ---- On Wed, 12 Jun 2019 21:24:31 +0800 Miguel de Benito Delgado > <m.debenito.delg...@gmail.com> wrote ---- > > There are at least four standard ways of ensuring dependencies are met: > > 1. python package manager (pip) on top of the OS installation. Not nice since > installs are OS wide. > (pip is itself a python package which we can assume is available as long as > there is a python distribution installed ( after 3.something it's installed > by default, otherwise it's trivial to install) ) > 2. virtualenv <https://docs.python.org/3/tutorial/venv.html>. Per user, local > installs in one directory, including specific python binaries, using pip. > AFAIK the "venv" module is also included in python installs by default. > 3. conda. Same as virtualenv but allowing for other binary dependencies > (libraries). miniconda <https://docs.conda.io/en/latest/miniconda.html> is > lightweight and pretty much a standard > 4. containerised solutions (docker + first item in this list). Does not apply > to our case. > > IMO virtualenv is the way to go in TeXmac's case since it is itself a python > package and we won't need any 3rd party libraries (non-python). But maybe > someone else has another suggestion? I always do the fourth, so I rarely use > virtualenv. > > I'm afraid I really cannot help out now, I'm sorry :( Maybe in a couple of > months.. > > -- > Miguel de Benito. > > > On Wed, 12 Jun 2019 at 11:29, Massimiliano Gubinelli <m.gubine...@gmail.com > <mailto:m.gubine...@gmail.com>> wrote: > Dear all, > > I was looking at the jupyter protocol, in view of integrating it with > TeXmacs. Instead of reimplementing everything (which seems quite complex) we > could try to modify the jupyter console here > > https://github.com/jupyter/jupyter_console > <https://github.com/jupyter/jupyter_console> > > to make it output the TeXmacs plugin protocol instead that using standard > output, in this way we can call it from TeXmacs and have jupyter kernels at > our disposal. This will make available many other systems inside TeXmacs. > > It should not be very difficult but I need some help since I’m not very > familiar with python. In particular I do not undestand how we should do: > surely we want to branch the jupyter console to have our own version adapted > to TeXmacs protocol, but in order for it to run it would need to have some > other packages available (like the one implementing the jupyter protocol, and > some other, like for example pygments, to colorise code). How one can be sure > that these are available on the client machine? Is there a standard way to > require packages? Can one assume they are always installed? I have a very > poor understanding of Python ecosystems. > > Are you interested in join this effort? > > Miguel? Darcy? > > Best > Max > > > > _______________________________________________ > Texmacs-dev mailing list > Texmacs-dev@gnu.org <mailto:Texmacs-dev@gnu.org> > https://lists.gnu.org/mailman/listinfo/texmacs-dev > <https://lists.gnu.org/mailman/listinfo/texmacs-dev> > _______________________________________________ > Texmacs-dev mailing list > Texmacs-dev@gnu.org <mailto:Texmacs-dev@gnu.org> > https://lists.gnu.org/mailman/listinfo/texmacs-dev > <https://lists.gnu.org/mailman/listinfo/texmacs-dev> > > > _______________________________________________ > Texmacs-dev mailing list > Texmacs-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________ Texmacs-dev mailing list Texmacs-dev@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
