Re: Switching Default Python3 To Python3.5

On 31.12.2015 10:44, Scott Kitterman wrote: I went through the bad/unknown packages in the python3.5 transition tracker [1] and the remainder seems reasonable for doing the transition. Many of them only build support for the default python3 and so they will be bad until after they are rebuilt

Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...

Ant Dude writes: >> In short, it isn't recommended practise to use pip install with Debian, >> except for inside a virtualenv (or similar), as the packages can >> conflict with Debian packages - especially after a upgrade. > > Interesting. I did find a fix and it seems like

Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...

> >> In short, it isn't recommended practise to use pip install with Debian, > >> except for inside a virtualenv (or similar), as the packages can > >> conflict with Debian packages - especially after a upgrade. > > > > Interesting. I did find a fix and it seems like others had the same > >

Re: Request to join the Debian Python Modules Team

[Víctor Cuadrado Juan, 2016-01-01] > I would like to join the DPMT to maintain python-neovim [1][2] great! > [2]: http://mentors.debian.net/package/python-neovim http://mentors.debian.net/debian/pool/main/p/python-neovim/python-neovim_0.1.0-1.dsc * how about "Description: scripting Nvim

Joining python-modules

Hi everyone, I recently wanted to increase my debian contributions as a prospective maintainer. I've read the policy from https://python-modules.alioth.debian.org/policy.html and I accept it (in fact, I love the idea behind collaborative maintenance, collab-maint, and I subscribed to