Hi Timo, And the transition is now complete :-)
Best wishes, Julian On Tue, Jan 09, 2024 at 05:45:04PM +0000, Julian Gilbey wrote: > Hi Timo, > > Please can we hold back on uploading pytest 8 to unstable until the > current Python 3.12 transition is complete? It is entirely possible > that several of the packages that currently break with pytest 8 > already have newer upstream versions that address these issues, but > it's probably not wise to mix that in with the current transition. > > Best wishes, > > Julian > > On Mon, Jan 08, 2024 at 11:32:29PM +0100, Timo Röhling wrote: > > Hi, > > > > I recently uploaded the pre-release pytest 8.0.0~rc1 to experimental as an > > early warning for the breaking changes which typically happen on major > > version bumps. > > > > I've attached a dd-list of packages which exhibit autopkgtest regressions > > [1], with the intent of MBF'ing (with separate announcement) once pytest 8 > > is released. > > > > Typically, packages will fail if they > > - have deprecation warnings of type PytestRemovedIn8Warning, or > > - assume a particular pytest stdout/stderr output which might have > > changed, or > > - rely on the precise order in which pytest collects tests, especially the > > behavior of the pytest.Package collector. > > > > Please refer to the upstream changelog [2] for a complete list of breaking > > changes. > > > > > > Cheers > > Timo > > > > [1] https://qa.debian.org/excuses.php?experimental=1&package=pytest > > [2] https://docs.pytest.org/en/latest/changelog.html