Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Where to put docs of a -doc package for python 2 + 3 modules? Date: Tue, 13 Mar 2018 08:20:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Mar 13 07:16:34 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.958 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, GMAIL=1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 30 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:oigrW2D7qF++GORXso+I3lXx96I= X-Mailing-List: archive/latest/15634 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85o9js4f9f.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 13 Mar 2018 18:16:12 +1100 X-Original-Message-ID: <85o9js4f9f.fsf@benfinney.id.au> X-Original-References: <20180312101616.GA21465@fama> <20180312223017.GD10894@fama> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:10239 Ghislain Vaillant writes: > Definitely [do not name the documentation package ‘python3-foo-doc’], > indeed. The python- prefixes in python-foo and python-foo-doc are not > exactly equivalent. The former usage refers to the Python 2 > interpreter, the latter refers to Python *the language*. Yes, that's how I understand the distinction. Thank you for expressing that. > It's unfortunate our naming convention did not explicitly separate > between both as Arch packages do, whereby `python` is used for source > package and `python2` for binary packages targeting CPython 2.x. Yes. Another point: The name of the documentation package should not depend on whether there is a Python 2 library package. So, the presence or absence of ‘python-foo’ should not change the name of ‘python-foo-doc’. > Imo, we should just make it clear in policy that source packages > should be named `foo` or `python-foo`, and corresponding doc packages > should be named `foo-doc` or `python-foo-doc`. +1. -- \ "Those who will not reason, are bigots, those who cannot, are | `\ fools, and those who dare not, are slaves." —“Lord” George | _o__) Gordon Noel Byron | Ben Finney