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 eli.bendersky
Recipients amaury.forgeotdarc, belopolsky, dgreiman, eli.bendersky, ext-, gustavo
Date 2013-05-13.13:39:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For external APIs visible to user code, this can cause some compatibility problems and users may need to at the very least re-compile this code. So -1 here.

For new external APIs, having const wherever appropriate should be considered on a case by case basis.

For internal code this is a good idea, but I wouldn't go mass-slashing all the code base now replacing char* by const char*. Presenting some examples where this makes sense in particular would be interesting though. +0
Date User Action Args
2013-05-13 13:39:19eli.benderskysetrecipients: + eli.bendersky, amaury.forgeotdarc, belopolsky, gustavo, dgreiman, ext-
2013-05-13 13:39:18eli.benderskysetmessageid: <>
2013-05-13 13:39:18eli.benderskylinkissue1772673 messages
2013-05-13 13:39:18eli.benderskycreate