Skip to content

CI, TST: have a f2py-specific CI run and properly skip f2py tests elsewhere #25134

@mattip

Description

@mattip

From #25073 where @HaoZeke pointed out CI is currently not properly testing f2py on windows.

I believe the solution is to have a new CI job, where (some) f2py tests should be tested the way users would use them, i.e. by generating the meson build directory with the skeleton template and then running meson within with the right environment variables.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions