[issue37438] ConfigParser.set() docs should mention allow_no_value

[Joannah Nanjekye]

Change by Joannah Nanjekye :


--
nosy: +nanjekyejoannah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37438] ConfigParser.set() docs should mention allow_no_value

[Prateek Nayak]

Change by Prateek Nayak :


--
keywords: +patch
pull_requests: +14272
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/14455

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37438] ConfigParser.set() docs should mention allow_no_value

[Nick Coghlan]

New submission from Nick Coghlan :

Reviewing some code today, I came across a ConfigParser.set() call that only 
specified the section and key, with the value argument missing.

If you look at the ConfigParser.set() docs, this seems like incorrect code, as 
those docs indicate that the value argument is a required parameter: 
https://docs.python.org/3/library/configparser.html#configparser.ConfigParser.set

However, checking the code shows that:

1. "value" has a default value of None
2. if "allow_no_value" is passed to the constructor, passing "None" as the 
value will be interpreted as a request to add a key-only entry to the section 
with no equals sign

--
assignee: docs@python
components: Documentation
messages: 346813
nosy: docs@python, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: ConfigParser.set() docs should mention allow_no_value
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com