This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients docs@python, martin.panter, serhiy.storchaka
Date 2015-03-22.10:31:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This patch adds the PEP 457 positional-only slash “/” indicator to some function signatures in the documentation. I only looked at the the os, builtin, binascii, zlib and fcntl modules, and their functions where the documentation incorrectly suggests that they accept keyword arguments. For example, I changed

eval(expression, globals=None, locals=None)


eval(expression, globals=None, locals=None, /)


* Issue 22832: “fcntl” module changed to look like accepting keyword arguments
* Ongoing discussion: <>

There are many more instances where square brackets are used, or the arguments are mandatory. See the PEP for examples, but I do not think it is so important to “fix” them.

I also fixed parameter name mismatches that I discovered for a quite a few functions that do take keyword arguments.

One more thing I noticed, that I do not know how to fix, is the Argument Clinic signatures list invalid default values for zlib.compressobj(zdict=None) and os.utime(ns=None):

>>> zlib.compressobj(zdict=None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'NoneType' does not support the buffer interface
>>> os.utime("dummy", ns=None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: utime: 'ns' must be a tuple of two ints
Date User Action Args
2015-03-22 10:31:02martin.pantersetrecipients: + martin.panter, docs@python, serhiy.storchaka
2015-03-22 10:31:01martin.pantersetmessageid: <>
2015-03-22 10:31:01martin.panterlinkissue23738 messages
2015-03-22 10:31:01martin.pantercreate