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


Groups > comp.lang.python > #20025

Re: when to use import statements in the header, when to use import statements in the blocks where they are used?

From Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject Re: when to use import statements in the header, when to use import statements in the blocks where they are used?
Date 2012-02-08 09:53 -0500
References <CACUCHEBhLhCCLL3OOudBKnuD2BZJvDkYzjmoi_nsVR+JPzEENA@mail.gmail.com> <4F31D85B.4040406@davea.name> <CACUCHECoeiU4QfqZJSnd+n9vcORWq=oOFP-aSSS-FayBwhR28g@mail.gmail.com> <4F31E0ED.30908@davea.name>
Newsgroups comp.lang.python
Message-ID <mailman.5545.1328713215.27778.python-list@python.org> (permalink)

Show all headers | View raw


On Tue, 07 Feb 2012 21:41:49 -0500, Dave Angel <d@davea.name> wrote:


>
>I can't speak for django or django-celery.  There are people that 
>disagree on this, and there are some reasons to override the ones I 
>mentioned.  One would be large modules that are not used in most 
>circumstances, or not used till the program has run for a while.
>
	Especially if the modules are OS-dependent... 
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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


Thread

Re: when to use import statements in the header, when to use import statements in the blocks where they are used? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-02-08 09:53 -0500

csiph-web