[issue38446] Ambiguous signature for builtins.__build_class__

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue38446] Ambiguous signature for builtins.__build_class__

Pablo Galindo Salgado added the comment: > @pablogsal can we close it? Yup, thanks for the ping, Batuhan -- ___ Python tracker ___

[issue38446] Ambiguous signature for builtins.__build_class__

Batuhan added the comment: This issue is fixed with PR 16735, @pablogsal can we close it? -- nosy: +BTaskaya, pablogsal ___ Python tracker ___

[issue38446] Ambiguous signature for builtins.__build_class__

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +16314 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16735 ___ Python tracker

[issue38446] Ambiguous signature for builtins.__build_class__

Change by Ivan Levkivskyi : -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker ___ ___

[issue38446] Ambiguous signature for builtins.__build_class__

New submission from Dan Snider : The function has the following signature documented: __build_class__(func, name, *bases, metaclass=None, **kwds) This implies that `func` and `name` are not positional only parameters when in fact, they are. Another problem with that signature is that