py3: do not include the notebook documentation in sage

[fchapoton]

because sagenb is not yet available for python3

CC: @embray @jdemeyer @tscrim @kiwifb @vbraun @kcrisman @jhpalmieri

Component: notebook

Author: John Palmieri

Branch: 591e91a

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/25382

[fchapoton]

Commit: 501b4d2

[fchapoton]

comment:2

I have no clear idea about what should be done here. Where will the sagenb doc live, if we get rid of it ?

---

New commits:

501b4d2

trying to remove sagenb doc

[fchapoton]

Branch: public/25382

[embray]

comment:3

Are we never going to get sagenb working in Python 3? I've just been assuming that for now we don't have it, but that we would eventually port it at least for now. Or are we truly abandoning sagenb for Python 3?

[fchapoton]

comment:4

Well, if somebody wants to do the job of converting sagenb to full python3 compatibility.. I have no idea of the difficulty of the task.

[vbraun]

comment:5

I'm fine with removing sagenb when we drop Python2 support unless somebody wants to port it... The SageNB docs should just say that (and suggest to use the jupyter notebook)

[kcrisman]

comment:6

If the ETA is still some time from now for Py2 drop that seems plausible. But hopefully it won't be that bad; I feel like #22431 was closer than we thought.

[fchapoton]

comment:7

We should try in the ticket #22431 to see if we can re-activate sagenb in py3-sage. We decided some time ago to de-activate it as it was blocking the build of py3-sage. Try to-re-insert sagenb requires first #24269 to fix py3-sage. Then rewrite the spkg-install on top of #25394.

On the side-point to get rid of sagenb imports inside sage, tt would be helpful to positive-review #24994.

[fchapoton]

comment:8

let us close this one as invalid, as we are on the way towards building the doc on py3, including sagenb doc