If you don't want to include the `standard` optional dependencies, you can install with `pip install fastapi` instead of `pip install "fastapi[standard]"`.

### Without `fastapi-cloud-cli` { #without-fastapi-cloud-cli }

If you want to install FastAPI with the standard dependencies but without the `fastapi-cloud-cli`, you can install with `pip install "fastapi[standard-no-fastapi-cloud-cli]"`.

      <prefix>deploy</prefix>
      <artifactId>maven-deploy-plugin</artifactId>
    </plugin>
    <plugin>
      <name>Maven Integration Test Plugin</name>
      <prefix>install</prefix>
      <artifactId>maven-install-plugin</artifactId>
    </plugin>
    <plugin>
      <name>Maven Integration Test Plugin</name>
      <prefix>jar</prefix>
      <artifactId>maven-jar-plugin</artifactId>
    </plugin>

public class LifecycleTaskSegmentCalculatorStub extends DefaultLifecycleTaskSegmentCalculator {
    public static final String CLEAN = "clean";

    public static final String AGGR = "aggr";

    public static final String INSTALL = "install";

    public LifecycleTaskSegmentCalculatorStub() {
        super(null, null);
    }

    @Override
    public List<TaskSegment> calculateTaskSegments(MavenSession session, List<String> tasks)

            </configuration>
          </execution>
          <execution>
            <id>install</id>
            <phase>generate-sources</phase>
            <goals>
              <goal>set</goal>
              <goal>attach-pom</goal>
              <goal>install</goal>
            </goals>
            <configuration>
              <mainFile>dependency-1.jar</mainFile>
            </configuration>

Pero en caso de que los necesites para un escenario avanzado, puedes agregar headers personalizados:

{* ../../docs_src/handling_errors/tutorial002_py39.py hl[14] *}

## Instalar manejadores de excepciones personalizados { #install-custom-exception-handlers }

@Singleton
public final class BomLifecycleMappingProvider extends AbstractLifecycleMappingProvider {
    // START SNIPPET: bom
    private static final String[] BINDINGS = {
        "install", "org.apache.maven.plugins:maven-install-plugin:" + INSTALL_PLUGIN_VERSION + ":install",
        "deploy", "org.apache.maven.plugins:maven-deploy-plugin:" + DEPLOY_PLUGIN_VERSION + ":deploy"
    };
    // END SNIPPET: bom

    @Inject

            plugins.add(newPlugin("maven-surefire-plugin", "test"));
            plugins.add(newPlugin("maven-jar-plugin", "jar"));
            plugins.add(newPlugin("maven-install-plugin", "install"));
            plugins.add(newPlugin("maven-deploy-plugin", "deploy"));
        } else {
            plugins = Collections.emptySet();
        }

        return plugins;
    }

    - name: Set up Python 3.9
      uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 # v6.1.0
      with:
        python-version: "3.9"
    - name: Install Python dependencies
      run: |
        python -m pip install --upgrade pip
        pip install pylint==2.13.9 numpy wheel
    - name: Run PyLint on changed files
      run: |

            plugins.add(newPlugin("maven-surefire-plugin", "test"));
            plugins.add(newPlugin("maven-jar-plugin", "jar"));
            plugins.add(newPlugin("maven-install-plugin", "install"));
            plugins.add(newPlugin("maven-deploy-plugin", "deploy"));
        } else {
            plugins = Collections.emptySet();
        }

        return plugins;
    }

ProjectDependencyGraphStub

Since they define the primary structure of the project/build.

The stubs define three top-level targets that are defined in  LifecycleTaskSegmentCalculatorStub;
clean, aggr and install. "aggr" is an aggregating task while clean and install are lifecyclephases.
There will be three items in the task list for this dataset.

The stubs also exist at different "levels", where one test might wire stubs into a specific live implementation.