fluffy = Cat(name="Mr Fluffy")
```

In diesem Fall ist `fluffy` eine Instanz der Klasse `Cat`.

Und um `fluffy` zu erzeugen, rufen Sie `Cat` auf.

Eine Python-Klasse ist also auch ein **Callable**.

Darum können Sie in **FastAPI** auch eine Python-Klasse als Abhängigkeit verwenden.

Was FastAPI tatsächlich prüft, ist, ob es sich um ein „Callable“ (Funktion, Klasse oder irgendetwas anderes) handelt und ob die Parameter definiert sind.

fluffy = Cat(name="Mr Fluffy")
```

Nesse caso,  `fluffy` é uma instância da classe `Cat`.

E para criar `fluffy`, você está "chamando" `Cat`.

Então, uma classe Python também é "chamável".

Então, no **FastAPI**, você pode utilizar uma classe Python como uma dependência.

O que o FastAPI realmente verifica, é se a dependência é algo chamável (função, classe, ou outra coisa) e os parâmetros que foram definidos.

# Classes as Dependencies { #classes-as-dependencies }

Before diving deeper into the **Dependency Injection** system, let's upgrade the previous example.

## A `dict` from the previous example { #a-dict-from-the-previous-example }

In the previous example, we were returning a `dict` from our dependency ("dependable"):

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

# Clases como dependencias { #classes-as-dependencies }

Antes de profundizar en el sistema de **Inyección de Dependencias**, vamos a mejorar el ejemplo anterior.

## Un `dict` del ejemplo anterior { #a-dict-from-the-previous-example }

En el ejemplo anterior, estábamos devolviendo un `dict` de nuestra dependencia ("dependable"):

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

# Классы как зависимости { #classes-as-dependencies }

Прежде чем углубиться в систему **Внедрения Зависимостей**, давайте обновим предыдущий пример.

## `dict` из предыдущего примера { #a-dict-from-the-previous-example }

В предыдущем примере мы возвращали `dict` из нашей зависимости:

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

Но затем мы получаем `dict` в параметре `commons` *функции-обработчика пути*.

     *       <td>{@code /home/user/myproject/target/classes}</td>
     *       <td>No explicit path → use output directory</td>
     *     </tr>
     *     <tr>
     *       <td>{@code Optional.of(Path.of("META-INF"))}</td>
     *       <td>{@code /home/user/myproject/target/classes}</td>
     *       <td>{@code /home/user/myproject/target/classes/META-INF}</td>

 * security protections against deserialization attacks. By default, it uses an
 * ObjectInputFilter to restrict which classes can be deserialized.
 * </p>
 * <p>
 * The default filter allows common safe classes like primitives, arrays, String,
 * Number types, collections, and classes in the org.codelibs package. For custom
 * requirements, use the overloaded methods that accept a custom filter.
 * </p>
 *
 * @author higa

    void testTargetPath() {
        Build build = mock(Build.class);
        when(build.getDirectory()).thenReturn("target");
        when(build.getOutputDirectory()).thenReturn("target/classes");
        when(build.getTestOutputDirectory()).thenReturn("target/test-classes");

        Project project = mock(Project.class);
        when(project.getBuild()).thenReturn(build);
        when(project.getBasedir()).thenReturn(Path.of("myproject"));

     *       <td>{@code target/classes}</td>
     *       <td>Compiled application classes and processed main resources</td>
     *     </tr>
     *     <tr>
     *       <td>{@link ProjectScope#TEST}</td>
     *       <td>{@code build.getTestOutputDirectory()}</td>
     *       <td>{@code target/test-classes}</td>
     *       <td>Compiled test classes and processed test resources</td>
     *     </tr>

            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <instructions>
            <!-- Silence a warning that claims that META-INF/versions/9/... is the "wrong directory" for our classes. -->
            <_fixupmessages>^Classes found in the wrong directory: .*</_fixupmessages>