///

## Erros das dependências e valores de retorno { #dependencies-errors-and-return-values }

Você pode utilizar as mesmas *funções* de dependências que você usaria normalmente.

### Requisitos de Dependências { #dependency-requirements }

Dependências podem declarar requisitos de requisições (como cabeçalhos) ou outras subdependências:

{* ../../docs_src/dependencies/tutorial006_an_py39.py hl[8,13] *}

 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>
 *     <li>{@code pom}: Indicates that the project does not produce a deployable artifact but is used for dependency management or as an aggregator.</li>
 *     <li>{@code maven-plugin}: Packages the project as a Maven plugin.</li>
 * </ul>
 *
 * <h2>Usage Example</h2>
 *
 * <pre>
 * {@code

        // Otherwise we get
        // ask ':tooling-api:publishGradleDistributionPublicationToRemoteRepository' uses this output of task ':tooling-api:signLocalPublication'
        // without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
        tasks.named("publishGradleDistributionPublicationToRemoteRepository") {
            dependsOn("signLocalPublication")

    "crossVersionTests": false
  },
  {
    "name": "dependency-management",
    "path": "platforms/software/dependency-management",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "dependency-management-serialization-codecs",
    "path": "platforms/core-configuration/dependency-management-serialization-codecs",
    "unitTests": false,

import org.apache.maven.artifact.versioning.InvalidVersionSpecificationException;
import org.apache.maven.artifact.versioning.VersionRange;
import org.apache.maven.model.Dependency;
import org.apache.maven.model.Exclusion;
import org.apache.maven.model.Plugin;
import org.apache.maven.model.Repository;
import org.apache.maven.model.RepositoryPolicy;

        assertEquals(weight1, weight2, "Project weight should be consistent");
    }

    @Test
    void testDependencyChainLength() {
        // Test that projects with longer dependency chains get higher weights
        // In the stub: A -> B,C; B -> X,Y; C -> X,Z
        long weightA = comparator.getProjectWeight(ProjectDependencyGraphStub.A);

    assert global_state["session_closed"] is True
    assert global_state["named_session_closed"] is True


def test_broken_scope() -> None:
    with pytest.raises(
        FastAPIError,
        match='The dependency "get_named_func_session" has a scope of "request", it cannot depend on dependencies with scope "function"',
    ):

        @app.websocket("/broken-scope")
        async def get_broken(

   ({{{./maven-core/xref/org/apache/maven/model/plugin/DefaultLifecycleBindingsInjector.html}source}})

   ** dependency management import (for dependencies of type <<<pom>>> and scope <<<import>>> in the <<<\<dependencyManagement\>>>> section)

   ** dependency management injection: <<<DependencyManagementInjector>>> ({{{./apidocs/org/apache/maven/model/management/DependencyManagementInjector.html}javadoc}}),

{* ../../docs_src/security/tutorial002_an_py310.py hl[5,12:6] *}

## Создать зависимость `get_current_user` { #create-a-get-current-user-dependency }

Давайте создадим зависимость `get_current_user`.

Помните, что у зависимостей могут быть подзависимости?

`get_current_user` будет иметь зависимость от того же `oauth2_scheme`, который мы создали ранее.

from starlette.datastructures import UploadFile as StarletteUploadFile


class UploadFile(StarletteUploadFile):
    """
    A file uploaded in a request.

    Define it as a *path operation function* (or dependency) parameter.

    If you are using a regular `def` function, you can use the `upload_file.file`
    attribute to access the raw standard Python file (blocking, not async), useful and
    needed for non-async code.