It would be nice to add some tests that use the new keywords associate block critical enum team, even if to make sure the words are not mispelled. I don't understand why tests would not be needed.

It would be nice to add some tests that use the new keywords associate block critical enum team, even if to make sure the words are not mispelled. I don't understand why tests would not be needed.

The corresponding statements have no influence on f2py output, they are just ignored. Even when misspelled they are ignored but with a "Mismatch of blocks encountered" warning. Technically, f2py does not implement Fortran parser and so it does not have to be exact in details that it never uses. In fact, in this particular case, there is nothing to test: with or without this PR f2py produces a correctly working code. So, adding the corresponding tests would just add maintenance burden to numpy, waste CI resources, and slow down f2py development, IMHO.

Sometimes such tests would not be even possible when the Fortran compiler used for testing does not implement the features of the latest Fortran standard but f2py can be still used in wrapping such codes.

I am confused. If "with or without this PR f2py produces correctly working code", then why do we need it? The original issue starts with "f2py break with functions/subroutines containing associate construct." So does it break or not?

No, it does not break.

The PR is needed for updating a piece of f2py to newer Fortran standards that did not exist at the time of creating f2py. The PR is maintenance PR, not a new-feature or a bug-fix PR.

I guess this is to handle code like this (from here)

program associateTest

  implicit none
  integer :: a=1,b=1
  someName: associate( x => a*b )
    print *, x                ! yields: 1
    a=10
    print *, x                ! yields: 1
  end associate someName

end program associateTest

So should the regex also allow an optional name fragment after end associate?

Yes, the relevant regular expressions also allow optional names after end <blockname>, see

As said before, those end statements are ignored by f2py, see

Thanks @pearu