[issue14739] Add PyArg_Parse format unit like O& but providing context

Irit Katriel added the comment: Now we have exception chaining, so Serhiy's pattern is even simpler to implement than with exception wrappers. -- nosy: +iritkatriel ___ Python tracker __

[issue14739] Add PyArg_Parse format unit like O& but providing context

Changes by Georg Brandl : -- nosy: +georg.brandl, loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue14739] Add PyArg_Parse format unit like O& but providing context

Serhiy Storchaka added the comment: It would be better if the functions PyArg_Parse* were wrapped converter's exception, in other exception with adding the names of function and parameter in the message. This will save us from necessity of the introduction of the new interface and immediately

[issue14739] Add PyArg_Parse format unit like O& but providing context

Changes by Larry Hastings : -- components: +Interpreter Core stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___ P

[issue14739] Add PyArg_Parse format unit like O& but providing context

Changes by Larry Hastings : -- assignee: -> larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue14739] Add PyArg_Parse format unit like O& but providing context

New submission from Larry Hastings : If you write a PyArg_Parse "converter", and your conversion hits an error, you must raise an exception and error out. But, since your converter has no context about the parameter, it can't provide any helpful information in the error. For example, PyUnico