FilesExpand file tree

 master

/

test_packages.py

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

50 lines (38 loc) · 2.58 KB

 master

/

test_packages.py

Copy path

Top

File metadata and controls

• Code
• Blame

50 lines (38 loc) · 2.58 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

"""Packages.

@see: https://docs.python.org/3/tutorial/modules.html#packages

Packages are a way of structuring Python’s module namespace by using “dotted module names”. For

example, the module name A.B designates a submodule named B in a package named A. Just like the

use of modules saves the authors of different modules from having to worry about each other’s

global variable names, the use of dotted module names saves the authors of multi-module packages

like NumPy or Pillow from having to worry about each other’s module names.

The __init__.py files are required to make Python treat the directories as containing packages;

this is done to prevent directories with a common name, such as string, from unintentionally hiding

valid modules that occur later on the module search path. In the simplest case, __init__.py can

just be an empty file, but it can also execute initialization code for the package or set the

__all__ variable, described later.

"""

# The __init__.py files are required to make Python treat the directories as containing packages;

# this is done to prevent directories with a common name, such as string, from unintentionally

# hiding valid modules that occur later on the module search path. In the simplest case,

# __init__.py can just be an empty file, but it can also execute initialization code for the

# package or set the __all__ variable, described later.

# Users of the package can import individual modules from the package, for example.

import sound_package.effects.echo

# An alternative way of importing the submodule is:

# pylint: disable=reimported

from sound_package.effects import echo

# Yet another variation is to import the desired function or variable directly:

from sound_package.effects.echo import echo_function

# Note that when using from package import item, the item can be either a submodule (or subpackage)

# of the package, or some other name defined in the package, like a function, class or variable.

# The import statement first tests whether the item is defined in the package; if not, it assumes

# it is a module and attempts to load it. If it fails to find it, an ImportError exception is

# raised.

# Contrarily, when using syntax like import item.subitem.subsubitem, each item except for the last

# must be a package; the last item can be a module or a package but can’t be a class or function or

# variable defined in the previous item.

def test_packages():

"""Packages."""

assert sound_package.effects.echo.echo_function() == 'Do echo effect'

assert echo.echo_function() == 'Do echo effect'

assert echo_function() == 'Do echo effect'