Marc-Andre Lemburg <m...@egenix.com> added the comment: On 2009-01-06 15:57, Alexander Belopolsky wrote: > Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment: > > On Tue, Jan 6, 2009 at 7:28 AM, Martin v. Löwis <rep...@bugs.python.org> > wrote: > .. >> It is not easier, but more difficult. It now requires a change, >> whereas leaving things as-is requires no change. > > I actually agree with Martin on this one. I would not touch this if > not for the Py_ssize_t vs. int issue. I am only +0 on renaming: if > type change and format spec changes go in, renaming is cost free.
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. _______________________________________ 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
