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


Groups > comp.lang.python > #20025 > unrolled thread

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

Started byDennis Lee Bieber <wlfraed@ix.netcom.com>
First post2012-02-08 09:53 -0500
Last post2012-02-08 09:53 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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

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

FromDennis Lee Bieber <wlfraed@ix.netcom.com>
Date2012-02-08 09:53 -0500
SubjectRe: when to use import statements in the header, when to use import statements in the blocks where they are used?
Message-ID<mailman.5545.1328713215.27778.python-list@python.org>
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/

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web