AbstractPointPen and GLIFPointPen use different argument names

[jenskutilek]

Type-checking code found this inconsistency:

Stubs/fontTools/ufoLib/glifLib.pyi:25: error: Signature of "addComponent" incompatible with supertype "AbstractPointPen"  [override]
Stubs/fontTools/ufoLib/glifLib.pyi:25: note:      Superclass:
Stubs/fontTools/ufoLib/glifLib.pyi:25: note:          def addComponent(self, baseGlyphName: str, transform: Tuple[float, float, float, float, float, float], identifier: Optional[str] = ..., **kwargs: Any) -> None
Stubs/fontTools/ufoLib/glifLib.pyi:25: note:      Subclass:
Stubs/fontTools/ufoLib/glifLib.pyi:25: note:          def addComponent(self, glyphName: str, transformation: Tuple[float, float, float, float, float, float], identifier: Optional[str] = ..., **kwargs: Any) -> None

It looks like an easy fix, but who knows what may break ...

[anthrotype]

interesting. who made those typing stubs?

in any case, it's only the name of the parameters, not their type that is different b/w super and subclass. I think the subclass should use the same names as the superclass, not the other way around.

Send a PR and if anything blows up we'll find out

[jenskutilek]

I made some basic stubs to enable type checking for my own modules.

I’ve unified the argument names in #2919.

[anthrotype]

I made some basic stubs to enable type checking for my own modules.

nice! maybe we can add those hints directly inline in the python modules, I think @madig has already set up mypy on the CI.