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

Groups > comp.lang.python > #10445

Is it bad practise to write __all__ like that

Path csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <karim.liateni@free.fr>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.012
X-Spam-Evidence '*H*': 0.98; '*S*': 0.00; '"""': 0.07; 'readable': 0.09; 'think?': 0.09; 'api': 0.11; 'output': 0.11; '__all__': 0.16; 'from:addr:free.fr': 0.16; 'subject:bad': 0.16; 'sfxlen:2': 0.19; 'to:2**1': 0.21; 'input': 0.21; 'cheers': 0.23; 'to:addr:tutor': 0.32; 'to:addr:python-list': 0.34; 'header:User- Agent:1': 0.34; 'to:no real name:2**1': 0.37; 'hello,': 0.38; 'to:addr:python.org': 0.39; 'received:62': 0.67; 'subject:like': 0.67; 'subject:write': 0.84
Date Thu, 28 Jul 2011 13:32:12 +0200
From Karim <karim.liateni@free.fr>
Subject Is it bad practise to write __all__ like that
To tutor@python.org, python-list@python.org
MIME-version 1.0
Content-type text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding 7bit
User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.12
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.1567.1311852741.1164.python-list@python.org> (permalink)
Lines 20
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1311852742 news.xs4all.nl 23892 [2001:888:2000:d::a6]:58338
X-Complaints-To abuse@xs4all.nl
Xref x330-a1.tempe.blueboxinc.net comp.lang.python:10445

Show key headers only | View raw

Hello,

__all__ = 'api db input output tcl'.split()

or

__all__ = """
                api
                db
                input
                output
                tcl
                """.split()

for lazy boy ;o). It is readable as well.
What do you think?

Cheers
Karim

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

Thread

Is it bad practise to write __all__ like that Karim <karim.liateni@free.fr> - 2011-07-28 13:32 +0200
  Re: Is it bad practise to write __all__ like that Ben Finney <ben+python@benfinney.id.au> - 2011-07-28 21:52 +1000
  Re: Is it bad practise to write __all__ like that Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-07-28 14:29 +0200
    Re: Is it bad practise to write __all__ like that Karim <karim.liateni@free.fr> - 2011-07-28 15:00 +0200
    Re: Is it bad practise to write __all__ like that Ian Kelly <ian.g.kelly@gmail.com> - 2011-07-28 12:01 -0600
      Re: Is it bad practise to write __all__ like that Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-07-29 08:37 +0200
        Re: Is it bad practise to write __all__ like that Karim <karim.liateni@free.fr> - 2011-07-29 11:54 +0200
    Re: Is it bad practise to write __all__ like that Erik Max Francis <max@alcyone.com> - 2011-07-28 22:22 -0700
    Re: Is it bad practise to write __all__ like that "OKB (not okblacke)" <brenNOSPAMbarn@NObrenSPAMbarn.net> - 2011-07-29 18:49 +0000

csiph-web