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 lemburg
Recipients belopolsky, lemburg, loewis
Date 2009-01-06.15:53:47
SpamBayes Score 0.48777944
Marked as misclassified No
Message-id <49637E8A.6000905@egenix.com>
In-reply-to <d38f5330901060657u688953c0r2df5c7e22fc94af8@mail.gmail.com>
Content
On 2009-01-06 15:57, Alexander Belopolsky wrote:
> Alexander Belopolsky <belopolsky@users.sourceforge.net> added the comment:
> 
> On Tue, Jan 6, 2009 at 7:28 AM, Martin v. Löwis <report@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.
History
Date User Action Args
2009-01-06 15:53:48lemburgsetrecipients: + lemburg, loewis, belopolsky
2009-01-06 15:53:47lemburglinkissue4850 messages
2009-01-06 15:53:47lemburgcreate