Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Piotr =?utf-8?Q?O=C5=BCarowski?= Newsgroups: linux.debian.maint.python Subject: Re: Python Policy Date: Tue, 20 Oct 2015 00:40:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Oct 19 22:37:55 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.399 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, CAPINIT=0.5, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: Debian GNU/Linux (3.16.0-4-amd64) User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/13016 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151019223739.GJ15907@sar0.p1otr.com Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 20 Oct 2015 00:37:39 +0200 X-Original-Message-ID: <20151019223739.GJ15907@sar0.p1otr.com> X-Original-References: <20151019133137.6174ef07@limelight.wooz.org> <20151019190420.GA15907@sar0.p1otr.com> <871tcqec0n.fsf@prune.linuxpenguins.xyz> Xref: csiph.com linux.debian.maint.python:7704 [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 and policy that apply for that team. > > The wikis are not official policy, only the policy if official policy. > > I don't understand why we need two teams for Python in Debian. DPMT and > DAPT share this mailing list. The only significant difference I see is > one is using git and the other is using subversion. there is one HUGE difference, one is about packaging MODULES and the other one is packaging APPLICATIONS. One provides python-, python3- and/or pypy- packages, the other cannot do that. > There are packages that do not provide public modules that are aimed at > developers. I imagine there are also packages that are end user > applications that do provide public modules, for end user > programming. These end user's may require the first group of packages > aimed at developers too. if something installs into dist-packages, it should (I'd make it a "must", but it's just me) provide python-/python3-/pypy- binary package. Python application should not (again, "must" is much better here IMO) pollute global Python namespace -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645