Re: Request to join DPMT

2017-06-27 Thread Pierre-Elliott Bécue
Le mardi 27 juin 2017 à 20:34:41+0200, Pierre-Elliott Bécue a écrit :
> Hey,
> 
> I'm currently working on packaging mailman3 suite. The work was halted until
> 3.1 got out. Now that mailman3.1 is out, I'm back into business! But there
> is one missing dependency that requires to be packaged: aiosmtpd.
> 
> I offered Barry Warsaw to package it, and he suggested me that I should do
> it into DPMT, and push the git repo on git.debian.org. For now, it's on
> github: https://github.com/P-EB/python-aiosmtpd which is not the best
> solution.
> 
> I tend to agree, and I hereby ask if you could consider adding me to the DPM
> project on alioth. I'm currently neither developer nor maintainer, but I
> intend to work on this issue asap. :)
> 
> My alioth login is peb-guest.
> 
> I'm eager to provide more intel and answer potential questions.
> 
> Cheers!

I forgot to mention that I of course read the debian python modules team
policy and that I accept it.

Cheers,

-- 
PEB



Request to join DPMT

2017-06-27 Thread Pierre-Elliott Bécue
Hey,

I'm currently working on packaging mailman3 suite. The work was halted until
3.1 got out. Now that mailman3.1 is out, I'm back into business! But there
is one missing dependency that requires to be packaged: aiosmtpd.

I offered Barry Warsaw to package it, and he suggested me that I should do
it into DPMT, and push the git repo on git.debian.org. For now, it's on
github: https://github.com/P-EB/python-aiosmtpd which is not the best
solution.

I tend to agree, and I hereby ask if you could consider adding me to the DPM
project on alioth. I'm currently neither developer nor maintainer, but I
intend to work on this issue asap. :)

My alioth login is peb-guest.

I'm eager to provide more intel and answer potential questions.

Cheers!

-- 
PEB



Re: IPython/Jupyter plans for buster

2017-06-27 Thread Julien Puydt
Hi,

Le 27/06/2017 à 18:20, Ximin Luo a écrit :

> This assumes the Sage kernel would still work with a python3-only notebook... 
> I certainly hope so, if jupyter upstream are ready to drop the python2 
> notebook so quickly...

there's a good chance sagemath will end up using Python 3 too at some
not-too-remote moment...

Snark on #debian-python



Re: IPython/Jupyter plans for buster

2017-06-27 Thread Ximin Luo
Gordon Ball:
> I don't have more information than was in the [1] link below, but my reading 
> of it is:
> 
> 8<
> 
> All ipython/jupyter components will drop python 2.7 support from version 6.
> 
> For ipython, ipykernel and dependencies ipython-genutils, traitlets the 
> current, python-2.7 supporting branch gets extended support until July 2019 
> (needed to run user-level python 2.7 code).
> 
> For components the user is meant to use as an application rather than an 
> importable library (notebook, nbconvert) there will be no extended python 2 
> support.
> 
> For components which might be useful to other projects (jupyter-core, 
> jupyter-client, nbformat) there *might* be extended support of the current 
> branch, but it isn't clear.
> 
> 8<
> 
> I think we want to follow the same strategy: keep support for running python 
> 2 code in interactive sessions and notebooks as long as possible, but for 
> other parts like the notebook server which the user is not expected to import 
> from, we drop python 2 support when upstream no longer provides it.
> 
> Which interfaces in jupyter does sagemath use? Is it just a kernel or does it 
> import directly from notebook/nbformat/nbconvert, etc?
> 

SageMath heavily imports from IPython, ipykernel, ipywidgets, but imports from 
the "notebook" at only two points, as far as I can tell:

src/bin/sage-notebook:from notebook.notebookapp import main
src/sage/repl/ipython_kernel/install.py:from notebook.notebookapp 
import NotebookApp

The second one is a dependency check, that would be easy to patch out in Debian.

The first one would take a bit more work since it's a public-facing interface 
that "sage -n jupyter" should start up the app. We'd have to patch it so that 
the Sage python2 process calls an external python3 process, probably.

This assumes the Sage kernel would still work with a python3-only notebook... I 
certainly hope so, if jupyter upstream are ready to drop the python2 notebook 
so quickly...

There is also this:

src/sage/repl/ipython_kernel/install.py:from jupyter_core.paths import 
ENV_JUPYTER_PATH

which would also be easy to patch out in Debian, by hard-coding directly with 
the actual path.

> When you say (2), since I failed to number them originally, I think you meant:
> 
> split ipython source package,
> python-ipython stays as version 5.x,
> python3-ipython gets version 6.x from a new source package
> 
> (correct?)
> 

Yes, that's what I meant.

X

>>> [..]
>>>
>>> [1]:
>>> https://github.com/jupyter/roadmap/blob/master/accepted/migration-to-python-3-only.md
>>> [2]: http://www.python3statement.org/
>>>

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git



Re: django-cms in Debian?

2017-06-27 Thread W. Martin Borgert

Quoting Dominik George :

at Teckids, we are about to start using Django CMS for our website.

We have a policy to only use Debian stable/main if at all possible.


This is a very useful policy!


So I wonder whether there is a reason django-cms is not in Debian?
(Apart from "noone started maintaining it" ;)


No, it's just "work", as far as I know.


In other words, before I start packaging django-cms and its missing
dependencies, is there anything I should know?


Just read https://bugs.debian.org/516183, I'm sure I'm not the only
one who very much appreciates having Django CMS in Debian!

Cheers



django-cms in Debian?

2017-06-27 Thread Dominik George
Hi,

at Teckids, we are about to start using Django CMS for our website.

We have a policy to only use Debian stable/main if at all possible.

So I wonder whether there is a reason django-cms is not in Debian?
(Apart from "noone started maintaining it" ;)

In other words, before I start packaging django-cms and its missing
dependencies, is there anything I should know?

Cheers,
Nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Phone: +49 228 92934581 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature