Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #95294

Re: Ensure unwanted names removed in class definition

From Jussi Piitulainen <ei@kun.ei.invalid>
Newsgroups comp.lang.python
Subject Re: Ensure unwanted names removed in class definition
Date 2015-08-12 19:33 +0300
Organization A noiseless patient Spider
Message-ID <lf5si7otqkj.fsf@ling.helsinki.fi> (permalink)
References <mailman.102.1439370080.3627.python-list@python.org>

Show all headers | View raw


Ben Finney writes:

> How can I ensure incidental names don't end up in the class
> definition, with code that works on both Python 2 and Python 3?
>
> With the following class definition, the incidental names `foo` and
> `bar`, only needed for the list comprehension, remain in the `Parrot`
> namespace::
>
>     __metaclass__ = object
>
>     class Parrot:
>         """ A parrot with beautiful plumage. """
>
>         plumage = [
>                 (foo, bar) for (foo, bar) in feathers.items()
>                 if bar == "beautiful"]
>
>     assert hasattr(Parrot, 'plumage')  # ← okay, has the wanted name
>     assert not hasattr(Parrot, 'foo')  # ← FAILS, has an unwanted name
>     assert not hasattr(Parrot, 'bar')  # ← FAILS, has an unwanted name
[- -]
> How can I write the class definition with the list comprehension and
> *not* keep the incidental names — in code that will run correctly on
> both Python 2 and Python 3?

Make them an implementation detail:

    plumage = [
        (__foo__, __bar__) for (__foo__, __bar__) in feathers.items()
        if __bar__ == "beautiful" ]

Back to comp.lang.python | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Ensure unwanted names removed in class definition Ben Finney <ben+python@benfinney.id.au> - 2015-08-12 19:01 +1000
  Re: Ensure unwanted names removed in class definition Jussi Piitulainen <ei@kun.ei.invalid> - 2015-08-12 19:33 +0300

csiph-web