Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Tue, Jan 6, 2009 at 10:53 AM, Marc-Andre Lemburg <rep...@bugs.python.org> wrote: .. > I don't follow you: those symbols are not meant for public use anyway, > so we can easily change them without any "costs". The same goes for any > of the private, but still exported symbols in the API, ie. all _Py* > APIs. This is the same that I said: "renaming is cost free" if it is done together with the type change. Martin was right that there is cost associated with any change. The benefit of "completeness" for a specialized build would not justify even having this discussion IMO. On the other hand since the type change needs to be done in order to make the code correct on a 64 bit platform and compile without warnings with gcc, a patch is needed anyways. Since we are already paying the cost of change, renaming is free. There is no disagreement between you and me here. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4850> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
