notebook toolbar

Activate

index execution_count cell_type toolbar started_at completed_at source loc metadata outputs

index	execution_count	cell_type	source	loc	metadata	outputs
1	In	markdown	# making `__main__` a `__package__` to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables. # making `__main__` a `__package__` to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.	`{'data': {'text/html': 'making a \nto make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.\n'}}`	3	making a to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.
2	In 1	code	import pytest; from pathlib import Path `import pytest; from pathlib import Path`	`{}`	1	0 outputs.
3	In	markdown	there is a python file one directory up called `mkdocs.py`. we should be able to get at this file, and we will. our first transgression is not being a package. there is a python file one directory up called `mkdocs.py`. we should be able to get at this file, and we will. our first transgression is not being a package.	`{'data': {'text/html': 'there is a python file one directory up called mkdocs.py.\nwe should be able to get at this file, and we will. \nour first transgression is not being a package.\n'}}`	4	there is a python file one directory up called `mkdocs.py` . we should be able to get at this file, and we will. our first transgression is not being a package.
4	In 2	code	with pytest.raises(ImportError, match="attempted relative import with no known parent package"): from . import mkdocs `with pytest.raises(ImportError, match="attempted relative import with no known parent package"): from . import mkdocs`	`{}`	2	0 outputs.
5	In	markdown	to be a package we need `__package__` and `__path__` to be a package we need `__package__` and `__path__`	`{'data': {'text/html': 'to be a package we need __package__ and __path__\n'}}`	1	to be a package we need `__package__` and `__path__`
6	In 3	code	__package__, __path__ = __name__, [""] `__package__, __path__ = __name__, [""]`	`{}`	1	0 outputs.
7	In	markdown	the `__path__` contains the lookup directories for parts of the package; this is a feature of namespace packages AND where shit gets weird. now that we quack like a package we can attempt relative imports, but `mkdocs.py` is still out of reach. the `__path__` contains the lookup directories for parts of the package; this is a feature of namespace packages AND where shit gets weird. now that we quack like a package we can attempt relative imports, but `mkdocs.py` is still out of reach.	`{'data': {'text/html': 'the __path__ contains the lookup directories for parts of the package;\nthis is a feature of namespace packages AND where shit gets weird. \nnow that we quack like a package we can attempt relative imports,\nbut mkdocs.py is still out of reach.\n'}}`	5	the `__path__` contains the lookup directories for parts of the package; this is a feature of namespace packages AND where shit gets weird. now that we quack like a package we can attempt relative imports, but `mkdocs.py` is still out of reach.
8	In 4	code	with pytest.raises(ImportError, match="cannot import name 'mkdocs' from '__main__' \(unknown location\)"): from . import mkdocs `with pytest.raises(ImportError, match="cannot import name 'mkdocs' from '__main__' \(unknown location\)"): from . import mkdocs`	`{}`	2	0 outputs.
9	In	markdown	append the parent to the `__path__` append the parent to the `__path__`	`{'data': {'text/html': 'append the parent to the __path__\n'}}`	1	append the parent to the `__path__`
10	In 5	code	__path__ += [".."] `__path__ += [".."]`	`{}`	1	0 outputs.
11	In	markdown	and boom! `and boom!`	`{'data': {'text/html': 'and boom!\n'}}`	1	and boom!
12	In 6	code	from . import mkdocs#! `from . import mkdocs#!`	`{}`	1	0 outputs.
13	In	markdown	## how is this different from `sys.paths` it is probably not much different, but more a cheat code you can abuse at your own ⚠ ## how is this different from `sys.paths` it is probably not much different, but more a cheat code you can abuse at your own ⚠	`{'data': {'text/html': 'how is this different from \nit is probably not much different, but more a cheat code you can abuse at your own ⚠\n'}}`	3	how is this different from it is probably not much different, but more a cheat code you can abuse at your own ⚠

markdown

# making `__main__` a `__package__`

to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.

# making `__main__` a `__package__`

to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.


        {'data': {'text/html': 'making  a 
\nto make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.\n'}}

making a

to make an interactive computing session, or a python module generally, appear like a package we need to set two varaiables.

In 1

code

    import pytest; from pathlib import Path

    import pytest; from pathlib import Path

markdown

there is a python file one directory up called `mkdocs.py`.
we should be able to get at this file, and we will.

our first transgression is not being a package.

there is a python file one directory up called `mkdocs.py`.
we should be able to get at this file, and we will.

our first transgression is not being a package.


        {'data': {'text/html': 'there is a python file one directory up called mkdocs.py.\nwe should be able to get at this file, and we will.
\nour first transgression is not being a package.\n'}}

there is a python file one directory up called mkdocs.py . we should be able to get at this file, and we will.

our first transgression is not being a package.

In 2

code

    with pytest.raises(ImportError, match="attempted relative import with no known parent package"):
        from . import mkdocs

    with pytest.raises(ImportError, match="attempted relative import with no known parent package"):
        from . import mkdocs

markdown

to be a package we need `__package__` and `__path__`

to be a package we need `__package__` and `__path__`

to be a package we need __package__ and __path__

In 3

code

    __package__, __path__ = __name__, [""]

    __package__, __path__ = __name__, [""]

markdown

the `__path__` contains the lookup directories for parts of the package;
this is a feature of namespace packages  AND where shit gets weird.

now that we quack like a package we can attempt relative imports,
but `mkdocs.py` is still out of reach.

the `__path__` contains the lookup directories for parts of the package;
this is a feature of namespace packages  AND where shit gets weird.

now that we quack like a package we can attempt relative imports,
but `mkdocs.py` is still out of reach.


        {'data': {'text/html': 'the __path__ contains the lookup directories for parts of the package;\nthis is a feature of namespace packages  AND where shit gets weird.
\nnow that we quack like a package we can attempt relative imports,\nbut mkdocs.py is still out of reach.\n'}}

the __path__ contains the lookup directories for parts of the package; this is a feature of namespace packages AND where shit gets weird.

now that we quack like a package we can attempt relative imports, but mkdocs.py is still out of reach.

In 4

code

    with pytest.raises(ImportError, match="cannot import name 'mkdocs' from '__main__' \(unknown location\)"):
        from . import mkdocs

    with pytest.raises(ImportError, match="cannot import name 'mkdocs' from '__main__' \(unknown location\)"):
        from . import mkdocs

markdown

append the parent to the `__path__`

append the parent to the `__path__`

append the parent to the __path__

In 5

code

    __path__ += [".."]

    __path__ += [".."]

markdown

and boom!

and boom!

and boom!

In 6

code

    from . import mkdocs#!

    from . import mkdocs#!

markdown

## how is this different from `sys.paths`

it is probably not much different, but more a cheat code you can abuse at your own ⚠

## how is this different from `sys.paths`

it is probably not much different, but more a cheat code you can abuse at your own ⚠


        {'data': {'text/html': 'how is this different from 
\nit is probably not much different, but more a cheat code you can abuse at your own ⚠\n'}}

how is this different from

it is probably not much different, but more a cheat code you can abuse at your own ⚠