Re: F41 Change Proposal: Pytest 8 (self-contained)

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

 



I got a list of all packages BuildRequiring pytest using this command:

$ repoquery --repo=rawhide{,-source} --whatrequires python3-pytest --recursive | grep src$ | pkgname | sort | uniq > packages.txt

FreeIPA is not there because pytest build time dependency is disabled via bcond. 

On Mon, Apr 8, 2024 at 8:16 AM Alexander Bokovoy <abokovoy@xxxxxxxxxx> wrote:
On Суб, 06 кра 2024, Sandro wrote:
>On 05-04-2024 23:45, Aoife Moloney wrote:
>>== Summary ==
>>
>>Update to a new upstream release of pytest that is not completely
>>compatible with previous releases. Pytest 8 is a major upstream
>>release removing a lot of deprecated functions and introducing
>>breaking changes.
>
>I was wondering how this will pan out with the introduction of Python
>3.13, which is also planned for F41 and comes with its own set of
>breaking changes. Some of those affecting tests.
>
>The current test builds are run against Python 3.12. Will all Python
>packages also be tested against Python 3.13 with pytest 8 later on?
>Does that even make sense?
>
>Anyway, it's two major updates affecting the Python ecosystem, which
>are both aiming at F41. Maybe letting the dust settle on Python 3.13
>first and then updating pytest to the next major release will let
>package maintainers (and upstream) focus more. Just some food for
>thought.

On top of that, I wonder how the packages were chosen. FreeIPA is
missing in the test COPR at all (but freeipa-healthcheck is present).
FreeIPA is also missing in the list of affected packages. We do use
pytest and some of more complex pytest plugins (multihost, sourceorder),
also add our own extensions.

I filed an upstream issue to track Pytest 8:
https://pagure.io/freeipa/issue/9571


--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux