Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!1.eu.feeder.erje.net!border1.nntp.ams1.giganews.com!border2.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <20150513133422.78617956@bigbox.christie.dr>
References: <f25aa9d4-4025-457d-8072-5327c98db1bd@googlegroups.com> <CAPTjJmrtLoCGOAr+F1Q7zgzv3hUhvrVA3ADdaLe9mP9YSShi6Q@mail.gmail.com> <CALwzid=tsm9c6DWyQ+g72+uG_KM+eDQ2Be3Pgj5gj6sorhNGHw@mail.gmail.com> <CAPTjJmpDfdYZ1LXeHbHNTuv_L4vaNZXnz-yOffjc1sM8tAd1Uw@mail.gmail.com> <20150513133422.78617956@bigbox.christie.dr>
Date: Thu, 14 May 2015 12:03:49 +1000
Subject: Re: Python file structure
From: Chris Angelico <rosuav@gmail.com>
Cc: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.473.1431569039.12865.python-list@python.org>
Lines: 38
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:90600

On Thu, May 14, 2015 at 4:34 AM, Tim Chase
<python.list@tim.thechases.com> wrote:
> Usually mine look something like
>
>   def do_real_work(options, args):
>     ...
>   def main():
>     parser = [optparse,argparse,docopt]....
>     options, args = parser.parse_args()
>     do_real_work(options, args)
>   if __name__ == "__main__":
>     main()
>
> since my real-work function usually relies on configuration
> (sometimes this also includes a config-file or environment variables
> being munged into some "options" data structure).
>

Sure. I rather dislike the whole duplication that that entails,
though, so I try to have the functions themselves do their own
argparse config. To that end, I put together a new project on PyPI,
but have now deprecated it in favour of Clize; the upshot is that my
main function becomes trivial again:

https://github.com/Rosuav/LetMeKnow/blob/master/letmeknow.py

@command
def await(...):
    """argparse config comes from here"""

if __name__ == "__main__":
    clize.run(commands)

So it comes and goes a bit. If there's real content in your main(),
then by all means, separate it out from do_real_work; but if the work
is all done elsewhere, not much point with main().

ChrisA