[Python-Dev] PEP 8 updates/clarifications (original) (raw)
Ian Bicking ianb at colorstudy.com
Tue Dec 13 05:47:12 CET 2005
- Previous message: [Python-Dev] PEP 8 updates/clarifications
- Next message: [Python-Dev] PEP 8 updates/clarifications
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
You should put a blank line between each group of imports.
I would suggest that it should also say that all goes after imports. But otherwise it's all good; the Mailman style guide just goes into greater detail.
-- Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org
- Previous message: [Python-Dev] PEP 8 updates/clarifications
- Next message: [Python-Dev] PEP 8 updates/clarifications
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]