RetroSearch Browse

Wed Feb 23 00:30:01 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-February/108180.html

On Tue, Feb 22, 2011 at 6:18 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
..
> I don't think it's a good idea to backport visible API changes.
> (someone successfully compiling on 2.7.N could then have users
> complaining that compilation fails on 2.7.N-1).
> Moreover, it doesn't really fix a bug.

That was the argument that I voiced
http://bugs.python.org/issue1699259#msg119032, but I cannot really
think of the code that would be broken by changing the type of an API
function *argument* from char * to const char *.  Given that 2.7 is an
odd-ball with extended maintenance period, I am not sure "it doesn't
really fix a bug" argument is dispositive.   I am still -0 on
backport, however.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108180.html below:

[Python-Dev] Const-correctness in C-API Object Protocol