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 belopolsky
Recipients belopolsky, lemburg, loewis
Date 2009-01-06.16:27:08
SpamBayes Score 0.0
Marked as misclassified No
Message-id <d38f5330901060826n204906b9lc98cdf8f53e7f994@mail.gmail.com>
In-reply-to <49637E8A.6000905@egenix.com>
Content
On Tue, Jan 6, 2009 at 10:53 AM, Marc-Andre Lemburg
<report@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.
History
Date User Action Args
2009-01-17 12:14:32loewissetspambayes_score: 0.830059 -> 0.0
2009-01-06 16:27:09belopolskysetrecipients: + belopolsky, lemburg, loewis
2009-01-06 16:27:08belopolskylinkissue4850 messages
2009-01-06 16:27:08belopolskycreate