Skip to content

bpo-33504: fix wrong "versionchanged" #11712

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

Merged
methane merged 1 commit into from
Jan 31, 2019
Merged

bpo-33504: fix wrong "versionchanged" #11712

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions Doc/library/configparser.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -476,9 +476,9 @@ the :meth:`__init__` options:
... 'bar': 'y',
... 'baz': 'z'}
... })
>>> parser.sections() # doctest: +SKIP
>>> parser.sections()
['section1', 'section2', 'section3']
>>> [option for option in parser['section3']] # doctest: +SKIP
>>> [option for option in parser['section3']]
['foo', 'bar', 'baz']

* *allow_no_value*, default value: ``False``
Expand Down Expand Up @@ -921,7 +921,7 @@ ConfigParser Objects
providing consistent behavior across the parser: non-string
keys and values are implicitly converted to strings.

.. versionchanged:: 3.7
.. versionchanged:: 3.8
The default *dict_type* is :class:`dict`, since it now preserves
insertion order.

Expand Down Expand Up @@ -1199,7 +1199,7 @@ RawConfigParser Objects
names, and values via its unsafe ``add_section`` and ``set`` methods,
as well as the legacy ``defaults=`` keyword argument handling.

.. versionchanged:: 3.7
.. versionchanged:: 3.8
The default *dict_type* is :class:`dict`, since it now preserves
insertion order.

Expand Down