Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15402 > unrolled thread
| Started by | Timo Röhling <roehling@debian.org> |
|---|---|
| First post | 2024-01-08 23:40 +0100 |
| Last post | 2024-01-26 08:40 +0100 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Breaking changes in pytest 8 Timo Röhling <roehling@debian.org> - 2024-01-08 23:40 +0100
Re: Breaking changes in pytest 8 Julian Gilbey <julian@d-and-j.net> - 2024-01-09 18:50 +0100
Re: Breaking changes in pytest 8 Louis-Philippe Véronneau <pollo@debian.org> - 2024-01-09 19:30 +0100
Re: Breaking changes in pytest 8 Timo Röhling <roehling@debian.org> - 2024-01-09 20:00 +0100
Re: Breaking changes in pytest 8 Julian Gilbey <julian@d-and-j.net> - 2024-01-26 08:40 +0100
| From | Timo Röhling <roehling@debian.org> |
|---|---|
| Date | 2024-01-08 23:40 +0100 |
| Subject | Breaking changes in pytest 8 |
| Message-ID | <HU6rL-1Lj9-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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 -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
[toc] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2024-01-09 18:50 +0100 |
| Message-ID | <HUooF-1WtM-5@gated-at.bofh.it> |
| In reply to | #15402 |
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
[toc] | [prev] | [next] | [standalone]
| From | Louis-Philippe Véronneau <pollo@debian.org> |
|---|---|
| Date | 2024-01-09 19:30 +0100 |
| Message-ID | <HUp1o-1WWl-5@gated-at.bofh.it> |
| In reply to | #15404 |
On 2024-01-09 12:45, 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. Agreed! There currently a lot of instability caused by 3.12 transition and waiting a little bit would certainly make things easier to deal with :) -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org ⠈⠳⣄
[toc] | [prev] | [next] | [standalone]
| From | Timo Röhling <roehling@debian.org> |
|---|---|
| Date | 2024-01-09 20:00 +0100 |
| Message-ID | <HUpup-1X6H-5@gated-at.bofh.it> |
| In reply to | #15404 |
[Multipart message — attachments visible in raw view] — view raw
Hi Julian, * Julian Gilbey <julian@d-and-j.net> [2024-01-09 17:45]: >Please can we hold back on uploading pytest 8 to unstable until the >current Python 3.12 transition is complete? Sure! I'll keep it in experimental, and we can check what still needs fixing after the Python 3.12 dust has settled. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
[toc] | [prev] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2024-01-26 08:40 +0100 |
| Message-ID | <I0oYF-5EBB-3@gated-at.bofh.it> |
| In reply to | #15404 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web