Re: IPython/Jupyter plans for buster
Hey, it depends on the details.
I think (2) would be the best option, I think it's not worth the effect trying to set up an "alternatives" system, we have enough stuff to do already without needing to test all of this complexity.
One thing we have to watch out for, is if their LTS versions stays on older libraries that are incompatible with the newest versions (cough cough NPM, but also python libs might be affected). Hopefully this would only happen rarely.
Are they dropping python2 support for the core components as well? It would be pretty annoying to have to package two of *everything* just for python2 support. (SageMath definitely needs it.)
X
Gordon Ball:
> Hello
>
> We currently have IPython 5.1 in the archive.
>
> Upstream has announced [1][2] IPython/Jupyter 5.x as an LTS branch (36
> months support, ending July 2019), and the last version to support
> Python 2.7. The first releases of IPython 6 (supporting Python 3 only)
> are now available.
>
> There seem to be several possibilities:
>
> * Stick with 5.x only for this cycle
> * Stick with 5.x as the default for 2 and 3 and provide an alternative
> 6.x package for python 3
> * Stick with 5.x only for python 2.7 and create a separate ipython 6.x
> source package for python 3
>
> This decision probably only needs to be made for the "user visible"
> components of jupyter (ipython, ipykernel and their dependencies); the
> application/script parts (nbconvert, jupyter-notebook, qtconsole, etc)
> can probably be moved to be python 3 only when required.
>
> Gordon
>
> [1]:
> https://github.com/jupyter/roadmap/blob/master/accepted/migration-to-python-3-only.md
> [2]: http://www.python3statement.org/
>
> postscript: I've just pushed updates to git for several of the jupyter
> packages
> * ipython -> 5.4.0
> * jupyter-client -> 5.1.0
> * nbconvert -> 5.2.1 (blocked on pandocfilters >= 1.4)
> * ipykernel -> 4.6.1
>
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
Reply to: