bpo-20923 : [doc] Explain ConfigParser 'valid section name'#31359
bpo-20923 : [doc] Explain ConfigParser 'valid section name'#31359Vidhyavinu wants to merge 4 commits into
Conversation
Updated the "Supported INI File Structure" with the details for legal section name: "By default, a legal section name can be any string that does not contain '\\n' or ']'. To change this, see :attr:`ConfigParser.SECTCRE`."
|
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). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
| .. [1] Config parsers allow for heavy customization. If you are interested in | ||
| changing the behaviour outlined by the footnote reference, consult the | ||
| `Customizing Parser Behaviour`_ section. | ||
| :mod:`configparser` --- Configuration file parser |
There was a problem hiding this comment.
The diff looks as if you changed everything in the file - is there a whitespace issue?
It should show only what you changed.
There was a problem hiding this comment.
Yeah. There is some whitespace issue. So I again tried upstreaming from the main branch and redo the modification. But still it shows the same.
There was a problem hiding this comment.
Adding a comparison report with BeyondCompare. This will help to locate the changes done as a part of this commit:
There was a problem hiding this comment.
You need to sort this out in the PR. It won't be merged as it is now.
There was a problem hiding this comment.
Please review the file in my last commit.
Thanks
There was a problem hiding this comment.
It's the same as before. Look at the "files changed" tab on the PR.
There was a problem hiding this comment.
Closing this pull request and creating new one. Sorry for the inconvenience.
New one: #31413
|
Hi,
I signed and send the Agreement form.
The GitHub user name is also updated in b.p.o account.
Thanks,
Vidhya
…On Tue, Feb 15, 2022 at 10:31 AM the-knights-who-say-ni < ***@***.***> wrote:
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 <https://www.python.org/psf/contrib/contrib-form/>
(CLA).
Recognized GitHub username
We couldn't find a bugs.python.org (b.p.o) account corresponding to the
following GitHub usernames:
@Vidhyavinu <https://github.com/Vidhyavinu>
This might be simply due to a missing "GitHub Name" entry in one's b.p.o
account settings. This is necessary for legal reasons before we can look at
this contribution. Please follow the steps outlined in the CPython
devguide <https://devguide.python.org/pullrequest/#licensing> to rectify
this issue.
You can check yourself <https://check-python-cla.herokuapp.com/> to see
if the CLA has been received.
Thanks again for the contribution, we look forward to reviewing it!
—
Reply to this email directly, view it on GitHub
<#31359 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW57AGF6OXCBSJVBYMHIFLTU3JWVRANCNFSM5OO4BGHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This is a copy of the configparser.rst from main branch
…n#31359) Added the changes in ConfigParser.rst
4 participants
Updated the "Supported INI File Structure" with the details for legal section name: "By default, a legal section name can be any string that does not contain '\n' or ']'. To change this, see :attr:
ConfigParser.SECTCRE."https://bugs.python.org/issue20923