Re: "pytest" command is missing
On 11/5/20 1:03 PM, firstname.lastname@example.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:
>>> 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
>>> 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.