This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients Kevin.Norris, docs@python, martin.panter
Date 2016-01-20.10:29:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453285786.22.0.428021549097.issue26160@psf.upfronthosting.co.za>
In-reply-to
Content
Yes 2.7 is open for changes to the documentation like this, as is 3.5+.

It’s been a while since I looked at the tutorial. Does it even mention the “python -m” mode? I don’t think this is the right place to introduce it.

Perhaps it would be okay to just say relative imports are based on the _full_ name of the current module. It could be misleading saying “the name of the current package”, because the import could be relative to the a higher level parent package if more than one dot is specified. Then point out that relative imports won’t work with ``python file.py`` or interactive mode, but don’t mention “-m” (or the other ways to run scripts and modules).
History
Date User Action Args
2016-01-20 10:29:46martin.pantersetrecipients: + martin.panter, docs@python, Kevin.Norris
2016-01-20 10:29:46martin.pantersetmessageid: <1453285786.22.0.428021549097.issue26160@psf.upfronthosting.co.za>
2016-01-20 10:29:46martin.panterlinkissue26160 messages
2016-01-20 10:29:45martin.pantercreate