request to join

Hello, I would like to join the team (my alioth login is 'oorestisime-guest'). I've read the policy i accepted it and I am mostly interested, for the moment, in contributing to port some of the modules to Python 3, like i did recently for python-wtforms and flask-wtf. Thanks in advance, Orestis

Re: About OpenStack, Mailman3 and python-falcon update

On Sep 18, 2015, at 06:48 PM, Pierre-Elliott Bécue wrote: >I'm currently trying to package mailman3 suite, I started with mailman3 core >functionnalities, you can see the ITP here: > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799281 Thanks for working on this! > >But, mailman3-core

Re: Packaging the Jupyter project suite

Hi, Le vendredi 18 sept. 2015 à 14:52:53 (-0700), Thomas Kluyver a écrit : > On Fri, Sep 18, 2015, at 08:49 AM, Julien Puydt wrote: > > What is annoying is that some of the packages have a dependency chain > > going in some way, and an extra dependency chain going the other way. > > For a

About OpenStack, Mailman3 and python-falcon update

Good evening, I was suggested to start a thread here, even having already filled a bugreport. I'm currently trying to package mailman3 suite, I started with mailman3 core functionnalities, you can see the ITP here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799281 But, mailman3-core

Packaging the Jupyter project suite

Hi, I would like to package the Jupyter suite of software (ex-IPython). Of course, that makes quite a few packages to prepare, with a big dependency graph. I already sent a few ITP (pickleshare, traitlets), a few RFS (path.py), some are in NEW (ipython-genutils)... What is annoying is that