Skip to content

gh-89885: Add example for spam.Bar #91523

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 17, 2022
Merged

gh-89885: Add example for spam.Bar #91523

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9ec1c1c
Add example for spam.Bar
slateny Apr 14, 2022
0190cb9
Removed Bar for simpler example
slateny Apr 16, 2022
6b19168
Wrap line
slateny Apr 16, 2022
566c8b3
Apply suggestions from code review
slateny Apr 16, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions Doc/reference/import.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,21 +490,19 @@ submodule. Let's say you have the following directory structure::
spam/
__init__.py
foo.py
bar.py

and ``spam/__init__.py`` has the following lines in it::
and ``spam/__init__.py`` has the following line in it::

from .foo import Foo
from .bar import Bar

then executing the following puts a name binding to ``foo`` and ``bar`` in the
then executing the following puts name bindings for ``foo`` and ``Foo`` in the
``spam`` module::

>>> import spam
>>> spam.foo
<module 'spam.foo' from '/tmp/imports/spam/foo.py'>
>>> spam.bar
<module 'spam.bar' from '/tmp/imports/spam/bar.py'>
>>> spam.Foo
<class 'spam.foo.Foo'>

Given Python's familiar name binding rules this might seem surprising, but
it's actually a fundamental feature of the import system. The invariant
Expand Down