Moved check for invalid use of class-scoped TypeVar within a self annotation in __init__. It was previously reported under reportGeneralTypeIssues, but it's now moved to reportInvalidTypeVarUse. This was done to help typeshed maintainers migrate away from this pattern. python/typeshed#11780 (comment)

Author: erictraut

packages/pyright-internal/src/analyzer/checker.ts

@@ -6958,7 +6958,7 @@ export class Checker extends ParseTreeWalker {
                 typeVars.some((typeVar) => typeVar.scopeId === functionType.details.methodClass?.details.typeVarScopeId)
             ) {
                 this._evaluator.addDiagnostic(
-                    DiagnosticRule.reportGeneralTypeIssues,
+                    DiagnosticRule.reportInvalidTypeVarUse,
                     LocMessage.initMethodSelfParamTypeVar(),
                     paramInfo.typeAnnotation
                 );

packages/pyright-internal/src/tests/typeEvaluator3.test.ts

@@ -1536,7 +1536,7 @@ test('Constructor5', () => {
 test('Constructor6', () => {
     const analysisResults = TestUtils.typeAnalyzeSampleFiles(['constructor6.py']);
 
-    TestUtils.validateResults(analysisResults, 1);
+    TestUtils.validateResults(analysisResults, 0, 1);
 });
 
 test('Constructor7', () => {