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 SylvainDe
Recipients SylvainDe
Date 2017-06-10.23:06:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1497135979.63.0.672123503952.issue30627@psf.upfronthosting.co.za>
In-reply-to
Content
Follow-up for http://bugs.python.org/issue30600 which is itself a follow-up for http://bugs.python.org/issue30534 . Not quite sure what the process is in that situation : creating a new ticket or updating the old one ?


After working on http://bugs.python.org/issue30600 , I thought that maybe other functions not generated by the clinic would have the same issue. "git grep _PyArg_NoStackKeywords | grep -v clinic" gave me some place to look for and indeed:

Modules/_struct.c:    if (!_PyArg_NoStackKeywords("pack", kwnames)) {
Modules/_struct.c:    if (!_PyArg_NoStackKeywords("pack_into", kwnames)) {
Python/bltinmodule.c:    if (!_PyArg_NoStackKeywords("getattr", kwnames)) {
Python/bltinmodule.c:    if (!_PyArg_NoStackKeywords("next", kwnames)) {

These four functions have a not-so-good error message when called with keyword arguments (and this is a regression compared to other Python versions)

I have a fix ready to be suggested but:

 - I want to be sure that I had to create a new ticket

 - I suspect functions defined via the GEN_CONSTRUCTOR macro in  Modules/_hashopenssl.c have the same issue but I do not know how to test it. Any help is welcome.
History
Date User Action Args
2017-06-10 23:06:19SylvainDesetrecipients: + SylvainDe
2017-06-10 23:06:19SylvainDesetmessageid: <1497135979.63.0.672123503952.issue30627@psf.upfronthosting.co.za>
2017-06-10 23:06:19SylvainDelinkissue30627 messages
2017-06-10 23:06:19SylvainDecreate