This is best discussed on the actual ticket - https://trac.sagemath.org/ticket/32887
On Saturday, August 20, 2022 at 8:52:30 AM UTC-7 emanuel.c...@gmail.com wrote: > Le samedi 20 août 2022 à 17:45:44 UTC+2, dim...@gmail.com a écrit : > >> we cannot agree on the direction for sagetex. >> >> Matthias insists on conversation of it to a proper Python package, >> without a build dependency on make or ninja. I disagree - I spent time >> converting it to a Python package which uses ninja at build time - and in >> fact ninja IS available as Python package. So it is Python enough in my >> eyes. >> > > Is ninja already used in building (some part of) Sage ? > > >> On Sat, 20 Aug 2022, 16:06 Emmanuel Charpentier, <emanuel.c...@gmail.com> >> wrote: >> >>> I do not understand my installation of sagetex. As far as I understand >>> it, Sage will use the files accessible via >>> $SAGE_ROOT/venv/share/texmf/tex/latex/sagetex, and that’s what I >>> symlinked to my LaTeX setup (in /usr/local/share/tex/latex/ in a Debian >>> testing installation). >>> >>> However, this version differs sensibly from what can be cloned from the >>> github >>> repository <https://github.com/sagemath/sagetex>. Even the files are >>> differenty named : in the Sage installation : >>> >>> $ ls /usr/local/sage/venv/share/texmf/tex/latex/sagetex >>> CONTRIBUTORS __pycache__ sagetex.ins >>> example.tex remote-sagetex.dtx sagetexparse.py >>> extractsagecode.py remote-sagetex.py sagetex.sty >>> makestatic.py run-sagetex-if-necessary.py scripts.dtx >>> py-and-sty.dtx sagetex.dtx >>> >>> In the cloned repository (after extraction and doc recompilation) : >>> >>> $ ls >>> CONTRIBUTORS sagetex-extract.py sagetexparse.py >>> example.tex sagetex.glo sagetex.pdf >>> HACKING.md sagetex.gls sagetex.py >>> LICENSE sagetex.hd sagetex-remote.py >>> Makefile sagetex.idx sagetex-run.py >>> py-and-sty.dtx sagetex.ilg sagetex.sagetex.sage >>> README.md sagetex.ind sagetex.sty >>> remote-sagetex.dtx sagetex.ins scripts.dtx >>> sagetex.aux sagetex.log setup.py >>> sagetex_doctest.sage sagetex-makestatic.py test.sh >>> sagetex.dtx sagetex.out TODO >>> >>> The Pyton scripts are named differently. >>> >>> More specifically, I had issues with the path_to_sage variable, thus >>> set by the curent Sagemath version : >>> >>> # CHANGE THIS AS APPROPRIATE >>> path_to_sage = os.path.expanduser('~/bin/sage') >>> # or try to auto-find it: >>> # path_to_sage = subprocess.check_output(['which', 'sage']).strip() >>> # or just tell me: >>> # path_to_sage = '/usr/local/bin/sage' >>> >>> This didn’t work for me (the path_to_sage = >>> subprocess.check_output(['which', 'sage']).strip() was OK). >>> >>> This became totally different in the Github version. >>> >>> I suppose that’s why the Github version has not (yet) been installed in >>> the Sagemath release. Hence a couple question : >>> >>> - >>> >>> Is this version ready for use ? >>> - >>> >>> Can it replace the current version ? >>> - >>> >>> If so, how to install it ? (by `sage -pip install , I suppose…) >>> >>> Advice ? >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to sage-support...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sage-support/942e5f32-0aad-4136-8bba-f6e8fdb01077n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/sage-support/942e5f32-0aad-4136-8bba-f6e8fdb01077n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f20091bf-f5ff-4545-8a5a-7285e9e9e9a8n%40googlegroups.com.
