python2.7 jupyter out in gentoo

[François Bissey]

Gentoo has a source distribution is handling python packages in a way
that avoid duplication across python versions. It comes at a price
and this weekend a decision has been made to drop python 2.7 from the
jupyter stack. It was causing massive dependency resolution problems
for packages where upstream offers python3 only versions (ipython-6+
for example).

There are still python2.7 jupyter packages in the tree. But no maintenance
update will be offered on them and python3 only version are unmasked.

I may very well be forced to offer sage-on-gentoo as a python3 only
thing in the next month or so.

François

[Jeroen Demeyer]

On 2019-05-05 23:19, François Bissey wrote:
> I may very well be forced to offer sage-on-gentoo as a python3 only
> thing in the next month or so.

Note that you don't need the full "Jupyter stack" to run Sage. If it
makes things easier: you only need IPython and its dependencies.

If you want to run Sage under Jupyter, you can run Jupyter with Python 3
but the Sage kernel with Python 2 (this may not work 100% out of the
box, but it should be easy).

Jeroen.

[François Bissey]

I have given thought to both points. Unfortunately one
element of the jupyter stack in question is IPython.
There doesn’t seem to be a move to purge python2.7 version
yet but that may not last.

François

[Dima Pasechnik]

I'd like to see options to build sage exclusively with Python 2 or 3.
Having both in one build might be useful, but not always.

--with-pythonX=no/yes/system, with X in {2.3}

(for the time being "system" might mean that everything is happening
in the virtual environment of pythonX)

> --
> You received this message because you are subscribed to the Google Groups "sage-packaging" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-packagin...@googlegroups.com.
> To post to this group, send email to sage-pa...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-packaging/CFB16033-185E-48AD-B34E-BEE8755B440B%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[François Bissey]

I am currently building 8.8.beta4 with 2.7, 3.6 and 3.7. Doc building
default to highest version.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-packaging/CAAWYfq0PCf6eGwwrv99TA%2B0ZsOT_KO8xyXsx8vPfbLs90nQ3Ow%40mail.gmail.com.

[E. Madison Bray]

It should also be possible, at least in theory, to run `jupyter
console` with a Sage kernel (where jupyter console is Python 3 but the
Sage kernel is Python 2). I haven't tried this though and I'm not
sure how it compares to running sage normally. It might not work
quite the same.

I've been meaning to explore that possibility more though and see if I
can get it to work. It would be one way to make the Sage experience a
little smoother on Windows, since I could start a headless Sage kernel
in the background on startup, and then running "sage" would just
connect to the existing kernel with the Jupyter console interface.