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 ncoghlan
Recipients Malcolm Smith, brett.cannon, docs@python, eric.snow, ncoghlan
Date 2017-07-06.03:58:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499313489.24.0.268319834386.issue30840@psf.upfronthosting.co.za>
In-reply-to
Content
That part of the PEP was never implemented - relative imports have never been allowed to cross package boundaries in practice (which is also why "from . import sys" doesn't work as an equivalent to "import sys" at the interactive prompt or in a top level module).

Rather than amending the PEP, my inclination is to drop that cross-reference from the documentation, and instead add a new subsection to https://docs.python.org/3/reference/import.html covering "Package relative imports"

The key section that needs to be extracted is https://www.python.org/dev/peps/pep-0328/#guido-s-decision (minus the part about cross-package relative imports being permitted).

The following section about __name__ is also worth including but needs to be updated to account for __package__ (added by PEP 366), and __spec__ (added by PEP 451).
History
Date User Action Args
2017-07-06 03:58:09ncoghlansetrecipients: + ncoghlan, brett.cannon, docs@python, eric.snow, Malcolm Smith
2017-07-06 03:58:09ncoghlansetmessageid: <1499313489.24.0.268319834386.issue30840@psf.upfronthosting.co.za>
2017-07-06 03:58:09ncoghlanlinkissue30840 messages
2017-07-06 03:58:08ncoghlancreate