Path: csiph.com!xmission!news.samoylyk.net!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ole Streicher Newsgroups: linux.debian.maint.python Subject: Re: Move to salsa? Merge modules and apps team? Date: Wed, 07 Feb 2018 11:40:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Feb 7 10:33:09 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.751 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_FROM_IP=-2 (check from: .ath. - helo: .liska.ath. - helo-domain: .ath.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7 Organization: The Borribles User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Lines: 28 X-Mailing-List: archive/latest/15509 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ytzd11hcdi9.fsf@news.ole.ath.cx Approved: robomod@news.nic.it Sender: robomod@news.nic.it X-Original-Date: Wed, 07 Feb 2018 11:14:54 +0100 X-Original-Message-ID: X-Original-References: <20180207073745.GA18829@fama> <20180207092936.4vzwdl7meqirpn3x@sar0.p1otr.com> Xref: csiph.com linux.debian.maint.python:10115 Piotr Ożarowski writes: > [W. Martin Borgert, 2018-02-07] >> And how about merging the modules and apps teams into one? > > I don't understand this, though. Why you want to merge them? > Sure, packaging Python applications is very similar to packaging > libraries but the difference is very significant - unfortunately many > application maintainers don't know or care about it and pollute global > Python namespace with private libraries. So, why would you like to keep them separate? > If not separated at team level, I definitely want to have them somehow > separated at repository level so that it's clear which package is which > type or to easily checkout libraries only. At least in the field where I package (astronomy), this does not work: many of our packages are libraries *and* apps. Often they come as a big (public) library with a small startup wrapper, and it is a matter of taste (and of how deep an astronomer digs into Python) whether it is used from the shell or from a Jupyter notebook. The rules for both are (should be) the same, right? So, what is the difference? Best regards Ole