PyArg_ParseTupleAndKeywords supports required keyword only arguments

[llllllllll]

BPO	30180
Nosy	@serhiy-storchaka, @llllllllll, @zhangyangyu
PRs	trivial: PyArg_ParseTupleAndKeywords supports required keyword only arguments #1290

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2017-04-27.00:51:02.518>
labels = ['docs']
title = 'PyArg_ParseTupleAndKeywords supports required keyword only arguments'
updated_at = <Date 2017-05-01.06:16:33.348>
user = 'https://github.com/llllllllll'

bugs.python.org fields:

activity = <Date 2017-05-01.06:16:33.348>
actor = 'xiang.zhang'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-04-27.00:51:02.518>
creator = 'llllllllll'
dependencies = []
files = []
hgrepos = []
issue_num = 30180
keywords = []
message_count = 1.0
messages = ['292385']
nosy_count = 4.0
nosy_names = ['docs@python', 'serhiy.storchaka', 'llllllllll', 'xiang.zhang']
pr_nums = ['1290']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue30180'
versions = []

[llllllllll]

I opened a pr to remove a line in the docs about $ needing to follow | in PyArg_ParseTupleAndKeywords. In practice, you can just use a $ to create required keyword arguments which intuitively makes sense. I was told this should raise a SystemError; however, you can create required keyword only arguments in Python so I am not sure why we would want to fail when this is done with PyArg_ParseTupleAndKeywords.