On 03. 04. 19 20:47, Robert-André Mauchin wrote:
On Wednesday, 3 April 2019 20:20:58 CEST Miro Hrončok wrote:
> I'd like to update pytest as soon as possible to 4.3 (or 4.4 if agreed
> This update will bring a lot of small breakage (long deprecated stuff got
> removed), but it is needed for Python 3.8 support. And I'd rather deal with
breakage now than firefighting it in the 3.8 side tag in May/June.
> Relevant bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1671167
> Relevant PR: https://src.fedoraproject.org/rpms/pytest/pull-request/8
> Miro Hrončok
> Phone: +420777974800
> IRC: mhroncok
How many of these small breakages do you expect?
The amount of bugs blocking this at this point (incl. CLOSED, excluding pacage
reviews is 7:
I've built cca 250 packages in my Python 3.8 + pytest 4 Copr.
Cca 90 from them use pytest (based on a quick dirty grep).
This is not a very good statistics but let's say that if we predict this to 3662
Python packages tracked on portingdb and/or 440 packages buildrequiring pytest,
we can except 35-100 failed builds.
Will they mainly affect old unmaintained packages?
No, this already affects e.g. pip.
Problem is that a lot of upstreams pin pytest to a specific version.
Will these breakages be easy to solve in your opinion?
Half of the problems so far was trivial (e.g. renaming a setup.cfg section).
Others might be harder. I can offer help. Worst case, tests can be temporarily