Skip to content

bpo-35954: Clarify string conversion in ConfigParser #11918

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.

Sign up for GitHub

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

Open
remilapeyre wants to merge 7 commits into
base: main
Choose a base branch
from
+14 −0
Open

bpo-35954: Clarify string conversion in ConfigParser #11918

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
c8fff23
Convert key to string when accessing ConfigParser
Feb 18, 2019
3f84272
Revert "Convert key to string when accessing ConfigParser"
Jan 20, 2020
8ecc7bd
Document that keys are always strings
Jan 20, 2020
6489fad
Fix typo
remilapeyre Jun 1, 2020
7885da4
Move the remark in its own section
remilapeyre Jun 1, 2020
57c3fac
Reduce diff
remilapeyre Jun 1, 2020
5a6a8f7
Update Doc/library/configparser.rst
remilapeyre May 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Reduce diff
  • Loading branch information
@remilapeyre
remilapeyre committed Jun 1, 2020
commit 57c3fac03caefae7adb60be9cbed50fe43861eaa
3 changes: 1 addition & 2 deletions Doc/library/configparser.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,10 +139,9 @@ case-insensitive and stored in lowercase [1]_.
Supported Datatypes
-------------------


Config parsers do not guess datatypes of values in configuration files, always
storing them internally as strings. This means that if you need other
datatypes, you should convert on your own::
datatypes, you should convert on your own:

.. doctest::

Expand Down