-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resurrect "sage -sws2rst" via a pip-installable package sage_sws2rst #28838
Comments
comment:1
Is converting |
comment:2
It seems not directly: after a quick look, the script seems to parse the html page, but maybe it could try to parse the html that belongs to the .sws archive (not sure if it has the same structure). Let me CC Volker for a better understanding of what is doable. |
comment:3
Here is a first sketch. The moved files are not at the level of sage requirements, as many doctests are missing. If this matters for you, please take the job. New commits:
|
Branch: u/chapoton/28838 |
Commit: |
comment:4
Shouldn't this go to a subdirectory of |
comment:5
Salut Thierry. Feel free to put it anywhere you like. I am not going to do anything more here. |
comment:6
Ticket retargeted after milestone closed |
comment:8
outdated, sws stuff was removed in #30076 |
comment:9
It is even more important now that there is no |
comment:10
it needs sagenb, a non-starter. |
Reviewer: Dima Pasechnik |
comment:11
Replying to @dimpase:
It only needs a small part of it (see Frédéric's patch), and the feature is still needed. |
comment:73
Great! Let me add a commit... |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:75
I am trying to run the tests with SAGE_CHECK, but before that I now get
Same thing if I run |
comment:76
Ah, sorry, I'll fix that |
comment:77
So if I undo the change -#! /usr/bin/env bash
+#! /bin/sh then I am able to
Indeed, where is the |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:80
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:82
Good.
Seems good! |
comment:83
In a folder with the following makefile:
then
gives only very few warnings:
It is true, that sometimes it does not translates the html properly. For instance, the following paragraph appears in the file CIRM_Tutorial_3.rst:
but I am quite sure it was the same problem before. From me it is a positive review. Let's deal with blockquote and other missing styles in another ticket if somebody finds it desirable. |
comment:85
|
comment:89
Docbuild is fixed, back to positive review |
Changed branch from public/28838 to |
An important feature is to still be able to handle old
.sws
worksheets because a lot of pedagogical material was written on that format.With the removal of sagenb, also
sws2rst
disappeared, see #30076 and related tickets.We extract and translate the required material from
sagenb
to a new optional packagesage_sws2rst
that makessage -sws2rst
work.As of this ticket, the source code of
sage_sws2rst
is inbuild/pkgs/sage_sws2rst/src
, which is a pip-installable Python package; and one can build an sdist from there, for example using thespkg-src
script. The source tree could as well be split out to a separate repository.See also:
CC: @vbraun @dimpase @kcrisman @jhpalmieri
Component: python3
Author: Frédéric Chapoton, Matthias Koeppe, Sébastien Labbé
Branch/Commit:
c026892
Reviewer: Dima Pasechnik, Sébastien Labbé, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/28838
The text was updated successfully, but these errors were encountered: