diff options
author | Brian Faherty <anothergenericuser@gmail.com> | 2022-02-17 12:17:43 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-02-17 12:17:43 (GMT) |
commit | fc115c9bde52a58b4fb9be2b80c3d6be8a4d2454 (patch) | |
tree | 0bff1ede5007a36651d434918f8b93d47e9a4c9e /.editorconfig | |
parent | 5bc4327e2c55c33342a6850c4741e2b63ff96aec (diff) | |
download | cpython-fc115c9bde52a58b4fb9be2b80c3d6be8a4d2454.zip cpython-fc115c9bde52a58b4fb9be2b80c3d6be8a4d2454.tar.gz cpython-fc115c9bde52a58b4fb9be2b80c3d6be8a4d2454.tar.bz2 |
bpo-41086: Add exception for uninstantiated interpolation (configparser) (GH-21062)
* Add exception for uninstantiated interpolation (configparser)
The current feedback when users try to pass an uninstantiated
interpolation into a ConfigParser is an error message that does not help
users solve the problem. This current error of `TypeError: before_set()
missing 1 required positional argument: 'value'` does not display until
the parser is used, which usually results in the assumption that
instantiation of the parser was done correctly. The new exception of
InterpolationTypeError, will be raised on the line where the
ConfigParser is instantiated. This will result in users see the line
that has the error in their backtrace for faster debugging.
There have been a number of bugs created in the issue tracker, which
could have been addressed by:
https://bugs.python.org/issue26831 and https://bugs.python.org/issue26469
* 📜🤖 Added by blurb_it.
* Replace custom Error with TypeError
Per feedback from @iritkatriel, the custom InterpolationTypeError has
been dropped in favour of a TypeError with a custom message, and the
unittests have been expanded.
* More verbose message
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Łukasz Langa <lukasz@langa.pl>
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions