Skip to content

bpo-44082: Add a method to check interpolation errors in configparser #26002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

bpo-44082: Add a method to check interpolation errors in configparser #26002

wants to merge 2 commits into from

Conversation

mun1r0b0t
Copy link

@mun1r0b0t mun1r0b0t commented May 9, 2021

The method is meant to check for errors in configuration file due to
missing or incorrect interpolation options. Currently, reading the
configuration file does not generate any error due to interpolation.
The documentation for this behaviour is also not very clear.

The method here provides a means to check for interpolation errors in
the configuration file. It can be used in unit tests or to create an
early failure in an application.

https://bugs.python.org/issue44082

The method is meant to check for errors in configuration file due to
missing or incorrect interpolation options. Currently, reading the
configuration file does not generate any error due to interpolation.
The documentation for this behaviour is also not very clear.

The method here provides a means to check for interpolation errors in
the configuration file. It can be used in unit tests or to create an
early failure in an application.
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

CLA Missing

Our records indicate the following people have not signed the CLA:

@munircontractor

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@github-actions
Copy link

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Jun 19, 2021
@github-actions github-actions bot removed the stale Stale PR or inactive for long period of time. label Aug 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants