`@classproperty` return type is not correctly resolved when used in a `@classmethod`

[HS-RAM]

Python version: 3.13.7
typed_classproperties version: 1.4.0
VSCode Pylance version: 2025.9.1

The return type of a @classproperty method is resolved as a classproperty instead of the return type hint given when accessed in a @classmethod.

Pylance reports: Type "classproperty" is not assignable to return type "int". "classproperty" is not assignable to "int" for the following sample code in method:

from typed_classproperties import classproperty


class MyClass:
    @classproperty
    def CLASSPROP(cls) -> int:
        return 1

    @classmethod
    def method(cls) -> int:
        return cls.CLASSPROP

When used in a non-classmethod context, the type is resolved correctly.

[CarrotManMatt]

Thanks for the bug report!

v1.4.0 of typed_classproperties was released recently; is this a regression you are experiencing compared to v1.3.2?

[HS-RAM]

I can't verify for v1.3.2, but it was also present in v1.3.1. I bumped to v1.4.0 to see if it was already resolved.

[CarrotManMatt]

Cheers, I'll spend some time investigating this. I have a gut feeling that it is related to the difference in type-checker implementations between mypy & pylance, as our type checker tests are only performed by mypy in CI.

[CarrotManMatt]

I've updated the policy on which type-checkers are officially supported (see https://github.com/CarrotManMatt/typed_classproperties/blob/main/README.adoc#supported-type-checkers). I'll leave this issue open and I'd be more than happy to accept any patches that fix this issue for your chosen alternative type-checker implementation. But, as this bug isn't reproducible on any of the supported type-checkers (currently just mypy) I won't personally be looking to contribute a fix.

The best solution for now would be to use the mypy VSCode extension rather than Pylance.

There is a manual workflow that has been run in CI displaying the results from running alternative type checker implementations upon the codebase.