RetroSearch Browse

Mon Dec 12 02:52:36 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-December/058562.html

On 12/11/05, Jim Fulton <jim at zope.com> wrote:
>
> Can we officially mark __private as a mistake. Perhaps:
>
> - Strongly discourage it in the style guide

This may be acceptable.

> - Mark it in the language reference as a deprecated feature
>
> - Generate deprecation warnings when it is used?
>    (This might be too much.)

I recently asked Guido about name mangling wrt Py3k.  He definitely
wanted to keep it in.  Unless he changed his mind, I doubt he would
deprecate it.  His rationale was that there needs to be a way to
handle name collision with multiple inheritance.

n

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/058562.html below:

[Python-Dev] Deprecate __ private (was Re: PEP 8 updates/clarifications)