Don't enforce @AbstractMethod and @coroutine consistency on properties.

See python/typeshed#6361.

PiperOrigin-RevId: 412119101

Author: rchen152

pytype/pyi/parser_test.py

@@ -2026,6 +2026,21 @@ def name(self) -> str: ...
           def name(self) -> int: ...
       """, 1, "Invalid property decorators for method `name`")
 
+  def test_abstract_property(self):
+    self.check("""
+      class Foo:
+        @property
+        @abstractmethod
+        def x(self) -> int: ...
+        @x.setter
+        def x(self, y: int) -> None: ...
+    """, """
+      from typing import Annotated
+
+      class Foo:
+          x: Annotated[int, 'property']
+    """)
+
 
 class MergeSignaturesTest(parser_test_base.ParserTestBase):
 

pytype/pytd/codegen/function.py

@@ -1,11 +1,10 @@
 """Function definitions in pyi files."""
 
 import collections
+import dataclasses
 
 from typing import Any, Dict, Iterable, List, Optional, Tuple
 
-import dataclasses
-
 from pytype.pytd import pytd
 
 
@@ -226,6 +225,10 @@ def add_overload(self, fn: NameAndSig):
       # For properties, we can have at most one of setter, getter and deleter,
       # and no other overloads
       self.add_property(fn.decorator, fn.signature)
+      # For properties, it's fine if, e.g., the getter is abstract but the
+      # setter is not, so we skip the @abstractmethod and  @coroutine
+      # consistency checks.
+      return
     elif self.decorator == fn.decorator:
       # For other decorators, we can have multiple overloads but they need to
       # all have the same decorator