Re: git instead of svn in DPMT policy

On Oct 17, 2015, at 08:49 PM, Piotr Ożarowski wrote: >I moved policy.rst to python-modules.git repo (it was available to edit >by every team member in SVN as well). It's not OK to edit it and push it >without having a discussion here (on this mailing list) first, though. I will make a pass

Re: Git migration schedule

Barry Warsaw writes: > My personal opinion is that we should live with the current git workflow > recommendations for a while and see how it goes. If there are things we can > improve on (e.g. DEP-14 compatibility) then sure, let's discuss the pros and > cons, but let's not

Re: Python Policy

| diff --git a/policy.rst b/policy.rst | index c09f03a..9a9abb4 100644 | --- a/policy.rst | +++ b/policy.rst | @@ -1,20 +1,19 @@ | - | - Python Modules Packaging Team - Policy | - |

Python Policy

So we currently have several places where we have team policy described. * The Debian wiki https://wiki.debian.org/Python and subpages * Another wiki page: https://wiki.debian.org/Teams/PythonModulesTeam * https://www.debian.org/doc/packaging-manuals/python-policy/ which comes from the

Re: Python Policy

[Barry Warsaw, 2015-10-19] > So we currently have several places where we have team policy described. no. Debian Python Policy¹ is something every single packages that extends Python should follow. There are many teams (more than 4) each of them can have their own policy that extends DPP.

Re: Python Policy

On October 19, 2015 1:31:37 PM EDT, Barry Warsaw wrote: >So we currently have several places where we have team policy >described. > >* The Debian wiki > https://wiki.debian.org/Python and subpages > >* Another wiki page: > https://wiki.debian.org/Teams/PythonModulesTeam >

Re: Python Policy

[Piotr Ożarowski, 2015-10-19] > DPMT and PAPT are two different things ups, PMPT != PAPT :) anyway, there are only documents each DPMT should know: * https://www.debian.org/doc/packaging-manuals/python-policy/ * https://python-modules.alioth.debian.org/policy.html everything else can help, but

Re: Python Policy

Piotr Ożarowski writes: > [Piotr Ożarowski, 2015-10-19] > > DPMT and PAPT are two different things > > ups, PMPT != PAPT :) So which of the following are redundant, and which names are canonical? * Debian Python Modules Team * Python Module Packaging Team * Debian Python

Re: Python Policy

[Ben Finney, 2015-10-19] > So which of the following are redundant, and which names are canonical? > > * Debian Python Modules Team > * Python Module Packaging Team these two are the same thing > * Debian Python Maintainers Team this doesn't exist AFAIK > For symmetry with “Python Application

Help needed: Bug#802354: python-matplotlib-venn: FTBFS: AttributeError: can't set attribute

Hi Python team, I have no idea why this package now fails to build but was building before. Any hint would be welcome Andreas. - Forwarded message from "Chris West (Faux)" - Date: Mon, 19 Oct 2015 19:05:55 +0100 From: "Chris West (Faux)"

Re: Python Policy

Barry Warsaw writes: > * "PMPT" policy > http://python-modules.alioth.debian.org/ > git+ssh://git.debian.org/git/python-modules/tools/python-modules.git Is policy.rst automatically kept in sync somehow in between python-modules.git and

Re: Python Policy

[Brian May, 2015-10-20] > Are DAPT and PAPT the same thing? no such thing as DAPT > This information should be documented somewhere. should we also document that we're not OpenStack Packaging Team? > In my words, for Debian project there is a wiki and a policy. For each > team there is a wiki

Re: DPMT Policy

[Brian May, 2015-10-19] > Barry Warsaw writes: > > > * "PMPT" policy > > http://python-modules.alioth.debian.org/ > > git+ssh://git.debian.org/git/python-modules/tools/python-modules.git > > Is policy.rst automatically kept in sync somehow in between > python-modules.git

Re: Python Policy

Piotr Ożarowski writes: >> * The Debian wiki >> https://wiki.debian.org/Python and subpages > > wiki is something everyone can edit. It's a place that can help with > various tasks, it can even be a place where policy is prepared, but it's > not a place to store official

Re: Git migration schedule

On Oct 18, 2015, at 07:19 PM, Jean-Michel Vourgère wrote: >Git multiple remotes is a nice feature. We can plug right into upstream >tree. Currently, our git workflow is tarball-based, since we primarily package PyPI releases, which are tarball-centric, and because orig.tar is required for