Skip to content

Don't use "import" in example method paths docs to avoid confusion#521

Merged
omab merged 1 commit intoomab:masterfrom
lamby:drop-import-module-from-docs
Feb 23, 2015
Merged

Don't use "import" in example method paths docs to avoid confusion#521
omab merged 1 commit intoomab:masterfrom
lamby:drop-import-module-from-docs

Conversation

@lamby
Copy link
Copy Markdown
Contributor

@lamby lamby commented Feb 16, 2015

This is for two reasons:

a) Using the verb "import" suggests that the module/function should be
imported which is not true; we want a "dotted path notation" string
rather than a reference to the method.

b) "import" is an invalid module name anyway, so as an example of dotted
path notation it is faulty. (Okay, it might actually be possible using
types and sys.modules but.. yeah)

Signed-off-by: Chris Lamb chris@chris-lamb.co.uk

This is for two reasons:

 a) Using the verb "import" suggests that the module/function should be
    imported which is not true; we want a "dotted path notation" string
    rather than a reference to the method.

 b) "import" is an invalid module name anyway, so as an example of dotted
    path notation it is faulty. (Okay, it might actually be possible using
    `types` and `sys.modules` but.. yeah)

Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
omab added a commit that referenced this pull request Feb 23, 2015
Don't use "import" in example method paths docs to avoid confusion
@omab omab merged commit d22abf1 into omab:master Feb 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants