```

Para saber mais sobre pacotes e módulos Python, leia [a documentação oficial do Python sobre módulos](https://docs.python.org/3/tutorial/modules.html).

///

### Evite colisões de nomes { #avoid-name-collisions }

Estamos importando o submódulo `items` diretamente, em vez de importar apenas sua variável `router`.

Isso ocorre porque também temos outra variável chamada `router` no submódulo `users`.

```Python
from app.routers import items, users
```

Python Packages와 Modules에 대해 더 알아보려면 [Modules에 대한 Python 공식 문서](https://docs.python.org/3/tutorial/modules.html)를 읽어보세요.

///

### 이름 충돌 피하기 { #avoid-name-collisions }

submodule `items`를 직접 import하고, 그 안의 `router` 변수만 import하지는 않습니다.

이는 submodule `users`에도 `router`라는 이름의 변수가 있기 때문입니다.

만약 다음처럼 순서대로 import했다면:

```Python

        }
    }

    @Test
    public void test_generate_invalid_parent_directory() throws Exception {
        // Create a path that's guaranteed to be invalid
        final File invalidParent = System.getProperty("os.name", "linux").toLowerCase().startsWith("windows")
                ? new File("Q:\\invalid\\path\\that\\does\\not\\exist")
                : new File("/invalid/path/that/does/not/exist");

If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).

10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses

```

Щоб дізнатися більше про пакети й модулі Python, прочитайте [офіційну документацію Python про модулі](https://docs.python.org/3/tutorial/modules.html).

///

### Уникайте колізій імен { #avoid-name-collisions }

Ми імпортуємо підмодуль `items` напряму, замість імпорту лише його змінної `router`.

Це тому, що в підмодулі `users` також є змінна з назвою `router`.

Якби ми імпортували один за одним, як:

     *   were fine, but they are still before one which reported errors.
     * <p>Then the returned value is {@code groupId:artifactId} when there is a name clash and
     * {@code :artifactId} if there is no conflict.
     * This method is made package-private for testing purposes.
     *
     * @param mavenProjects Maven projects which are part of build execution.

     *
     * (Currently it's safe to pass instances for which compareTo() always
     * returns 0, but if we had a SingletonImmutableSortedSet, this might no
     * longer be the case.)
     *
     * javax.naming.Name and java.util.concurrent.Delayed might work, but
     * they're fairly obscure, we've invented our own interface and class.
     */
    Interface a = new Impl();
    Interface b = new Impl();

pkg syscall (linux-arm-cgo), func Times(*Tms) (uintptr, error)
pkg syscall (linux-arm-cgo), func Truncate(string, int64) error
pkg syscall (linux-arm-cgo), func Umask(int) int
pkg syscall (linux-arm-cgo), func Uname(*Utsname) error
pkg syscall (linux-arm-cgo), func UnixCredentials(*Ucred) []uint8
pkg syscall (linux-arm-cgo), func UnixRights(...int) []uint8
pkg syscall (linux-arm-cgo), func Unlinkat(int, string) error

///

### Запустить Docker-контейнер { #start-the-docker-container }

* Запустите контейнер на основе вашего образа:

<div class="termy">

```console
$ docker run -d --name mycontainer -p 80:80 myimage
```

</div>

## Проверка { #check-it }

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles version="12">
<profile kind="CodeFormatterProfile" name="DBFlute Style" version="12">
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_ellipsis" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_new_line_in_empty_annotation_declaration" value="insert"/>