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.13:01:30
SpamBayes Score 0.41537502
Marked as misclassified No
Message-id <49635629.9020405@egenix.com>
In-reply-to <49634E62.3000109@v.loewis.de>
Content
On 2009-01-06 13:28, Martin v. Löwis wrote:
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> 
>> For completeness
> 
> I don't think completeness is a useful thing to have here.
> 
>> and to make things easier for all developers,
> 
> It is not easier, but more difficult. It now requires a change,
> whereas leaving things as-is requires no change.

Sure it does: consistent rules always make things easier, since
they avoid doubt.

>> all exported symbols should be prefixed with _Py or Py - regardless
>> of how their export is enabled.
> 
> Ah - but they aren't exported symbols.

I'm only referring to exported symbols. Static globals, of course,
don't need such a prefix.
History
Date User Action Args
2009-01-06 13:01:32lemburgsetrecipients: + lemburg, loewis, belopolsky
2009-01-06 13:01:30lemburglinkissue4850 messages
2009-01-06 13:01:30lemburgcreate