[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "pytest" command is missing

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.

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 ; \

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).


Thomas Goirand (zigo)

Reply to: