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 h.venev
Recipients h.venev
Date 2014-03-21.16:45:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395420316.16.0.247771357348.issue21011@psf.upfronthosting.co.za>
In-reply-to
Content
This really annoys me. I have to store the literals in char[] and then make a char*[] from them. It would be better if a simple array of string literals could be used. It would also require less data space because string literals could be merged by the compiler.

I don't know why PyArg_ParseTupleAndKeywords would ever modify the keywords array so it makes absolutely no sense to me for the array not to be const char*[].

In all cases I have seen PyArg_ParseTupleAndKeywords being used string literals were converted to char* (dropping const) which is far far worse than inefficient code.
History
Date User Action Args
2014-03-21 16:45:16h.venevsetrecipients: + h.venev
2014-03-21 16:45:16h.venevsetmessageid: <1395420316.16.0.247771357348.issue21011@psf.upfronthosting.co.za>
2014-03-21 16:45:16h.venevlinkissue21011 messages
2014-03-21 16:45:15h.venevcreate