Unable to utilise a module as a type. What is the alternative?

[RokeJulianLockhart]

Prerequisites

#!/usr/bin/env -S python3.13
import \
    builtins, \
    PyQt6.QtWidgets, \
    PyQt6.QtCore, \
    PyQt6.QtGui, \
    typing

Problem

Currently, I have:

def apply_resize_policy(object: PyQt6.QtWidgets) -> None:
    """
    Limits *resize*.
    """

    object.setSizePolicy(
        PyQt6.QtWidgets.QSizePolicy.Policy.Minimum,
        PyQt6.QtWidgets.QSizePolicy.Policy.Minimum
    )

Instead, I want to use what stackoverflow.com/revisions/46092347/5 recommends:

def apply_resize_policy(object: builtins.type[PyQt6.QtWidgets]) -> None:
    """
    Limits *resize*.
    """

    object.setSizePolicy(
        PyQt6.QtWidgets.QSizePolicy.Policy.Minimum,
        PyQt6.QtWidgets.QSizePolicy.Policy.Minimum
    )

However, I see:

Module cannot be used as a type

Diagnosis

Is this an example of issues/2704#issuecomment-993666444? I request confirmation because the discussion at that issue and its cited predecessor are somewhat too technical for me to be confident that I've correctly understood them.

[erictraut]

A type annotation specifies a set of valid objects for that parameter, variable, etc. It wouldn't make sense for a module to be used within a type annotation. What would that even mean?

I suspect what you mean here is that object must be an instance of PyQt6.QtWidgets.QWidget or a subclass thereof. If that's correct, then use PyQt6.QtWidgets.QWidget as the type annotation for `object.

For more information about type annotations, refer to the getting started documentation in pyright. You might also find the type system concepts chapter of the Python typing spec to be useful.

[RokeJulianLockhart]

I suspect what you mean here is that object must be an instance of PyQt6.QtWidgets.QWidget or a subclass thereof.

@erictraut, that's indeed what I'm attempting to accomplish, albeit solely for subclasses of it. I apologise for not explaining that, since it's fairly important to answering the question.

If that's correct, then use PyQt6.QtWidgets.QWidget as the type annotation for object.

Would that not indicate that the expected object is (an instance of) the module itself? If not, I appear to have misunderstood what the OP at the linked SO question is asking, although I'll be surprised if I have.

[erictraut]

It doesn't make sense to talk about an "instance of the module". A module isn't instantiable, so you can't create an instance of it. By contrast, class objects are instantiable.

[RokeJulianLockhart]

#9931 (reply in thread)

@erictraut, I wasn't aware. Thanks.

I presume that, consequently, the more verbose syntax (object: builtins.type[PyQt6.QtWidgets]) being redundant (because the user can solely ever want to refer to any class defined in the module, rather than an instance thereof) means that the type parser rejects it?

If so, not, instead, enforcing that the user write the object: builtins.type[PyQt6.QtWidgets], appears strange, considering that the behaviour would be more consistent than having the more concise syntax (object: PyQt6.QtWidgets) perform its function based upon context.

Relevantly, I realised whilst writing that I'd pasted the same example twice. It's now been rectified, but I'm surprised you understood my query regardless.