Message258659
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). |
|
Date |
User |
Action |
Args |
2016-01-20 10:29:46 | martin.panter | set | recipients:
+ martin.panter, docs@python, Kevin.Norris |
2016-01-20 10:29:46 | martin.panter | set | messageid: <1453285786.22.0.428021549097.issue26160@psf.upfronthosting.co.za> |
2016-01-20 10:29:46 | martin.panter | link | issue26160 messages |
2016-01-20 10:29:45 | martin.panter | create | |
|