[issue13180] pysetup silently ignores invalid entries in setup.cfg

Changes by Éric Araujo : -- resolution: -> out of date stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue13180] pysetup silently ignores invalid entries in setup.cfg

Éric Araujo added the comment: A side effect of this change will be the removal of the Extension class, which was only useful to do some typechecks/conversions on its arguments. In Python code it will be replaced by a dict (with keys 'name', 'sources', 'optional', etc.), and when building th

[issue13180] pysetup silently ignores invalid entries in setup.cfg

Éric Araujo added the comment: I want to explore ideas about a schema/type system, so I’m removing the easy keyword. -- keywords: -easy ___ Python tracker ___

[issue13180] pysetup silently ignores invalid entries in setup.cfg

Éric Araujo added the comment: Agreed. Doc/packaging/setupcfg.rst defines that custom fields need to start with X-, so we can refuse everything that is not built-in and does not start with X-. (I’m going toward error rather than warning.) -- assignee: tarek -> eric.araujo keywords:

[issue13180] pysetup silently ignores invalid entries in setup.cfg

New submission from Paul Moore : With a simple setup.cfg defining a distribution containing a single Python module, if you misspell the "modules" keyword (say, as "module") then pysetup does nothing without reporting the error. This silent failure is very hard to debug, and even if pysetup is