Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#970643: "pytest" command is missing Date: Thu, 05 Nov 2020 14:00:01 +0100 Message-ID: References: X-Original-To: "terceiro@debian.org" , 970643@bugs.debian.org, debian-python@lists.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Thu Nov 5 12:57:08 2020 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -4.2 Reply-To: Matthias Klose , 970643@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Python Team X-Debian-Pr-Message: followup 970643 X-Debian-Pr-Package: python3-pytest X-Debian-Pr-Source: pytest X-Spam-Bayes: score:0.0000 Tokens: new, 11; hammy, 150; neutral, 89; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--H*F:U*doko, 0.000-+--goirand, 0.000-+--Goirand, 0.000-+--H*RU:sk:einhorn Old-X-Envelope-From: doko@debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Debian-Message: from BTS X-Mailing-List: archive/latest/1630880 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 37 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 5 Nov 2020 13:53:28 +0100 X-Original-Message-ID: <6278f3e1-d159-65cc-b97b-5b0c136e126e@debian.org> X-Original-References: <0e5f7819-e98a-af39-a9c8-7ebee40a77d4@indigo.re> <44137225ad2b8f6d9561f51133c831a1be67b494.camel@firma.seznam.cz> <20201104170138.GA24212@debian.org> <286f72d69d871c2fcc5409df7d70af6ee57b2d89.camel@firma.seznam.cz> <4afd7f99-ecbf-b22d-ff53-55d7410a9157@debian.org> <20201105120338.GA6655@debian.org> <0e5f7819-e98a-af39-a9c8-7ebee40a77d4@indigo.re> <20201105120338.GA6655@debian.org> Xref: csiph.com linux.debian.bugs.dist:1031369 linux.debian.maint.python:13004 On 11/5/20 1:03 PM, terceiro@debian.org wrote: > On Thu, Nov 05, 2020 at 09:28:56AM +0100, Thomas Goirand wrote: >> On 11/4/20 9:27 PM, Novy, Ondrej wrote: >>> Hi, >>> >>> Antonio Terceiro píše v St 04. 11. 2020 v 14:01 -0300: >>>> Could you ellaborate? Maybe we should have a discussion in the Python >>>> team so that we implement consistent practices. For example, `gunicorn` >>>> and `pip` now point to their python3 versions, but you are saying that >>>> pytest will not do that, what maybe creates more confusion given Debian >>>> bullseye will not support any other Python. >>> >>> "pytest" in buster now points to python2 version of pytest and >>> "pytest-3" points to python3 version. To prevent confusion after upgrade >>> I want to keep one stable release with pytest cmd "unoccupied" and keep >>> pytest-3. >>> >>> Bullseye will support Python2 interpreter so user can keep python-pytest >>> package installed from buster. > > The python2 interpreter will be supported, but nothing else will, so I > don't see the point of this compatibility. I don't think that "keep you > old packages from the previous release" is a great upgrade path. well, afaiu, we also will ship python-pip, so that users are able to get their python2 code from other places. > Anyway, my point is that we should collective aim to be consistent > across the Python packages. The fact that some packages have made their > "not *3" binaries be the python3 versions, and others not, due to > arbitrary individual maintainer decisions, is a mess. it's a difficult decision to make. But if people want, then we could ship pytest-is-python2 and pytest-is-python3 packages as well, as long as we don't build-depend on those. Matthias