typeguard v4.2.1 prints out non-runtime protocol messages

[polothy]

Describe the bug

Recently upgraded aws-cdk-lib@v2.223.0 in a Python based project. This caused typeguard to upgrade from v2.13.3 to v4.2.1. On synth, getting many of these messages:

/path/to/.venv/lib/python3.13/site-packages/aws_cdk/aws_events/__init__.py:411: UserWarning: Typeguard cannot check the IRuleTarget protocol because it is a non-runtime protocol. If you would like to type check this protocol, please use @typing.runtime_checkable
  typeguard.check_type(value=value, expected_type=expected_type, collection_check_strategy=typeguard.CollectionCheckStrategy.ALL_ITEMS) # type:ignore

Might be related to #4658 but seems like that's another problem with typeguard (incompatible interfaces vs runtime protocol).

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

No messages from typeguard.

Current Behavior

typeguard prints these message:

/path/to/.venv/lib/python3.13/site-packages/aws_cdk/aws_events/__init__.py:411: UserWarning: Typeguard cannot check the IRuleTarget protocol because it is a non-runtime protocol. If you would like to type check this protocol, please use @typing.runtime_checkable
  typeguard.check_type(value=value, expected_type=expected_type, collection_check_strategy=typeguard.CollectionCheckStrategy.ALL_ITEMS) # type:ignore

Reproduction Steps

Use typeguard v4.2.1 in a Python CDK project, using latest aws-cdk-lib

Possible Solution

Workaround: pin typeguard to 2.13.3.

Additional Information/Context

No response

SDK version used

1.119.0

Environment details (OS name and version, etc.)

macOS

[techman83]

This seems to be related to the release of the upgrade to aws/constructs#2823, which includes a commit that that references that it might be fixed in agronholm/typeguard#465. And but the pr notes that jsii-pakmac pins to < 4.3.0 but that's clearly not the case.

jsii-1.119.0

    install_requires=[
        "attrs>=21.2,<26.0",
        "cattrs>=1.8,<25.4",
        "importlib_resources>=5.2.0",
        "publication>=0.0.3",  # This is used by all generated code.
        # 4.3.0 is incompatible with generated bindings, see https://github.com/aws/jsii/issues/4658
        "typeguard>=2.13.3,<4.5.0",  # This is used by all generated code.
        "python-dateutil",
        "typing_extensions>=3.8,<5.0",
    ],

[techman83]

Looking at the provider code generated, the solution is likely that regenerating the providers would solve this (I'm not in a spot to verify that right now).

def check_type(argname: str, value: object, expected_type: typing.Any) -> typing.Any:
    if TYPEGUARD_MAJOR_VERSION <= 2:
        return typeguard.check_type(argname=argname, value=value, expected_type=expected_type) # type:ignore
    else:
        if isinstance(value, jsii._reference_map.InterfaceDynamicProxy): # pyright: ignore [reportAttributeAccessIssue]
           pass
        else:
            if TYPEGUARD_MAJOR_VERSION == 3:
                typeguard.config.collection_check_strategy = typeguard.CollectionCheckStrategy.ALL_ITEMS # type:ignore
                typeguard.check_type(value=value, expected_type=expected_type) # type:ignore
            else:
                typeguard.check_type(value=value, expected_type=expected_type, collection_check_strategy=typeguard.CollectionCheckStrategy.ALL_ITEMS) # type:ignore

[techman83]

I can confirm that the tests I have failing were built before the check_type method was added. So rebuilding the providers should solve this.