RetroSearch Browse

Tue Dec 13 05:56:15 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-December/058659.html

On 12/12/05, Ian Bicking <ianb at colorstudy.com> wrote:
> skip at pobox.com wrote:
> > This is subjective enough that I would think some rationale explaining this
> > convention should be given.  Personally, I group imports into three sections
> > as follows:
> >
> >     * Python core modules/packages
> >
> >     * Third-party modules/packages
> >
> >     * Local modules/packages
>
> This is already in PEP 8:
>
>      - Imports are always put at the top of the file, just after any
>        module comments and docstrings, and before module globals and
>        constants.  Imports should be grouped, with the order being
>
>        1. standard library imports
>        2. related major package imports (i.e. all email package imports next)
>        3. application specific imports

Hm. I like Skip's list better; "related major package imports" is a
bit vague and ambiguous. It seems to have been written before email
became a standard library module; also it clearly meant to say "e.g."
instead of "i.e.".

>        You should put a blank line between each group of imports.
>
> I would suggest that it should also say that __all__ goes after imports.

+1

--
--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/058659.html below:

[Python-Dev] PEP 8 updates/clarifications