Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #20003
| Date | 2012-02-07 21:05 -0500 |
|---|---|
| From | Dave Angel <d@davea.name> |
| Subject | Re: when to use import statements in the header, when to use import statements in the blocks where they are used? |
| References | <CACUCHEBhLhCCLL3OOudBKnuD2BZJvDkYzjmoi_nsVR+JPzEENA@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5529.1328666724.27778.python-list@python.org> (permalink) |
On 02/07/2012 08:48 PM, Lei Cheng wrote: > Hi all, > > In a py file, when to use import statements in the header, when to use > import statements in the blocks where they are used? > What are the best practices? > Thanks! > > Pat > Best practice is to put all the imports at the beginning of the module, so they are easy to spot. If you put an import inside a function, it gets re-executed each time the function is called, which is a waste of time. Not too much, since import first checks sys.modules to see if it's already loaded. Also, avoid the from xxx import * form, as it pollutes the namespace. And it makes it hard to figure out where a particular name is declared. I believe these and other best practices can be found in pep8. http://www.python.org/dev/peps/pep-0008/ -- DaveA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: when to use import statements in the header, when to use import statements in the blocks where they are used? Dave Angel <d@davea.name> - 2012-02-07 21:05 -0500
csiph-web