Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: "terceiro@debian.org" Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#970643: "pytest" command is missing Date: Thu, 05 Nov 2020 13:10:02 +0100 Message-ID: References: X-Original-To: 970643@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Thu Nov 5 12:06:09 2020 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -4.2 Reply-To: "terceiro@debian.org" , 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, 12; hammy, 150; neutral, 96; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--H*ct:pgp-sha256, 0.000-+--goirand, 0.000-+--Goirand, 0.000-+--Python3 X-Originating-IP: 198.58.116.17 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline X-Greylist: delayed 68523 seconds by postgrey-1.36 at buxtehude; Thu, 05 Nov 2020 12:03:48 UTC X-Debian-Message: from BTS X-Mailing-List: archive/latest/1630871 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 71 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Thu, 5 Nov 2020 09:03:38 -0300 X-Original-Message-ID: <20201105120338.GA6655@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> <0e5f7819-e98a-af39-a9c8-7ebee40a77d4@indigo.re> <4afd7f99-ecbf-b22d-ff53-55d7410a9157@debian.org> Xref: csiph.com linux.debian.bugs.dist:1031360 linux.debian.maint.python:13003 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 05, 2020 at 09:28:56AM +0100, Thomas Goirand wrote: > 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 Debian > >> 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 upgrade > > 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-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. 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. > Moreover, simply invoking "pytest-3" is not enough, one should be using: >=20 > for pyvers in $$(py3versions -vr 2>/dev/null) ; do \ > python$$pyvers -m pytest ; \ > done >=20 > 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). Sure, but that only applies for package maintainance. People who just want to use pytest to test their Python code have a (IMO pointless) divergence from upstream. This made some sense when there were 2 supported Python ecosystems, but that's now in the past. We could take the opportunity to fix this. --jI8keyz6grp/JLjh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAl+j6hcACgkQ/A2xu81G C94RkhAAw+2iS7EYV2gjFVc3AnbQ3Ns5vgisMGzbkMptc3SVvIM0jbo3cGigyTeG Hk2cgdQW6AT9ZskOzaQcG+Zsd/57MyQObfqFNfVfV0XhBhyt4y/pxVtMCten47eb 7mTKD596VMV3IwLtJCqkuWqfPb85L+AEuOxVgXBDccKosowgMhz8Mc/tYR3M+DEn LBaLoFVmNLJaM4NvPr4TbNQD1nrzUXdk1iL33iHcTQBTZ6FJBsDnWdFdkHNlrClK fC0H6NU7JVwzcN9zbh47Bvir3VYUgEQR15051gtZOOJ0a8z51fcOgNX38vaHvnlt PgnxhA8Sl5YgcJO60YviiZAw72zm4VWSCA308AYXwrE8So28B6DyF7hwJHjcOvPZ x2vmnyYWfisVavVvLB6TCuEqbT1y+L3Z5pIGADXjCZUnmWLN9rdEW+unmSy5cJs4 63ZufunAZbos/3t1ufnDalpCV526YDj2XcRX7UOE1VK8yNryjjdjlNnCwaBaso9X ocnYAFCRzR06WBnZglWaS16E8UuotCeEAMoAi6fwQL88o9AA2lA7JTT8MnFT+m8g bQ2vNCdz3l1qUXxN8tQcM5DcwmzYbTk4rNRgksjVdszHKBgkM9pT/mQRuyNeiAnx aZARhyS9Tt1Ui5OJESsZTOo5x9WsVSGYEcDxkWh+a1CZkKSILuc= =DWL3 -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--