Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#970643: "pytest" command is missing Date: Thu, 05 Nov 2020 09:40:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Thu Nov 5 08:33:12 2020 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -4.2 Reply-To: Thomas Goirand , 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, 14; hammy, 150; neutral, 48; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--goirand, 0.000-+--Goirand, 0.000-+--Python3, 0.000-+--Python2 Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Debian-Message: from BTS X-Mailing-List: archive/latest/1630828 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 35 Sender: robomod@news.nic.it X-Original-Cc: "970643@bugs.debian.org" <970643@bugs.debian.org>, "debian-python@lists.debian.org" X-Original-Date: Thu, 5 Nov 2020 09:28:56 +0100 X-Original-Message-ID: <4afd7f99-ecbf-b22d-ff53-55d7410a9157@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> <0e5f7819-e98a-af39-a9c8-7ebee40a77d4@indigo.re> <286f72d69d871c2fcc5409df7d70af6ee57b2d89.camel@firma.seznam.cz> Xref: csiph.com linux.debian.bugs.dist:1031330 linux.debian.maint.python:13002 On 11/4/20 9:27 PM, Novy, Ondrej wrote: > Hi, >=20 > Antonio Terceiro p=C3=AD=C5=A1e 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 Debia= n >> bullseye will not support any other Python. >=20 > "pytest" in buster now points to python2 version of pytest and > "pytest-3" points to python3 version. To prevent confusion after upgrad= e > I want to keep one stable release with pytest cmd "unoccupied" and keep > pytest-3. >=20 > Bullseye will support Python2 interpreter so user can keep python-pytes= t > package installed from buster. Moreover, simply invoking "pytest-3" is not enough, one should be using: for pyvers in $$(py3versions -vr 2>/dev/null) ; do \ python$$pyvers -m pytest ; \ done otherwise, only the default version of Python3 is tested, and we really want to test with all available versions (so we get results whenever we're transitioning to a new Python 3 version). Cheers, Thomas Goirand (zigo)