Title: Const-Correctness for Method Calls
Type: behavior Stage: resolved
Components: None Versions: Python 3.2
Status: closed Resolution: duplicate
Dependencies: Superseder: const char* for PyObject_CallMethod and PyObject_CallFunction
View: 9369
Assigned To: Nosy List: aronacher, neXyon
Priority: normal Keywords: patch

Created on 2010-07-24 09:52 by aronacher, last changed 2010-07-24 11:16 by eric.araujo. This issue is now closed.

File name Uploaded Description Edit
const.patch aronacher, 2010-07-24 09:52 Patch for API + documentation
Messages (2)
msg111435 - (view) Author: Armin Ronacher (aronacher) * (Python committer) Date: 2010-07-24 09:52
The following patch changes some parts of the public C API for const correctness which would help C++ programmers.

The original patch was provided by neXyon on

It does not produce any compiler warnings on GCC and I don't expect any compiler warnings on other systems either.
msg111440 - (view) Author: Jörg Müller (neXyon) Date: 2010-07-24 10:04
Uhm, while I reported this Armin was faster than me :) However, I've merged our patches in issue9369.
Date User Action Args
2010-07-24 11:16:57eric.araujosetstatus: open -> closed
resolution: duplicate
superseder: const char* for PyObject_CallMethod and PyObject_CallFunction
stage: patch review -> resolved
2010-07-24 10:04:06neXyonsetnosy: + neXyon
messages: + msg111440
2010-07-24 09:52:57aronachercreate