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 signature.asc Description: OpenPGP digital signature
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 would depend on falcon version >= 0.3.0rc1 which is not >yet packaged in Debian. > >I filled a bug report here: > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799321 > >Thomas Goirand (zigo) answered to me something I perfectly understand, that >for now, zaqar, which is part of the python stuff used in OpenStack, depends >on falcon < 0.2.0, and thus can no longer be packaged in debian if we update >python-falcon. > >It seems he has contacted zaqar developers in hope to have them test zaqar >with falcon 0.3, and, if needed, patch it. The zaqar bug is this one, right? https://bugs.launchpad.net/zaqar/+bug/1495402 If so, I've commented and subscribed to that bug. Cheers, -Barry
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 concrete example, ipykernel depends on ipython... but ipython has > > an extra-dep on ipykernel. > > The extra deps in IPython are for backwards compatibility, so that if > people have scripted (or remembered) commands like "pip install > ipython[notebook]", they will continue to work, by pulling in the > separated package which now contains that functionality. In time we will > probably remove these. That is very comforting! > I'd recommend that you ignore these compatibility dependencies (that is, > all the extra dependency groups of IPython besides doc and test). Of those only testpath looks problematic (I filled an issue on it yesterday), so the future looks quite bright. Thanks, Snark on #debian-python
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 would depend on falcon version >= 0.3.0rc1 which is not yet packaged in Debian. I filled a bug report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799321 Thomas Goirand (zigo) answered to me something I perfectly understand, that for now, zaqar, which is part of the python stuff used in OpenStack, depends on falcon < 0.2.0, and thus can no longer be packaged in debian if we update python-falcon. It seems he has contacted zaqar developers in hope to have them test zaqar with falcon 0.3, and, if needed, patch it. I'm opening this thread to discuss about this, and possible solutions to this deadend, as I can no longer test anything nor continue packaging mm3. I could try to package my own python-falcon in my custom repo to see if my mailman3-core packaging works, but it could not go in Debian's repo anyway. As I'm a beginner, I certainly need some wisdom from people on debian-python@ Thanks for the time anyone will give to me, and apologies to bother. -- PEB
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 some of the packages have a dependency chain going in some way, and an extra dependency chain going the other way. For a concrete example, ipykernel depends on ipython... but ipython has an extra-dep on ipykernel. How does one package something like this? Does someone want to lend a hand? Thanks, Snark on #debian-python
