/// details | `.venv` or other name

You could create the virtual environment in a different directory, but there's a convention of calling it `.venv`.

///

## Activate the Virtual Environment { #activate-the-virtual-environment }

Activate the new virtual environment so that any Python command you run or package you install uses it.

/// tip

    <class java.clone="deep">
      <name>ActivationProperty</name>
      <version>1.0.0+</version>
      <description>
        This is the property specification used to activate a profile. If the value field is empty,
        then the existence of the named property will activate the profile, otherwise it does a case-sensitive
        match against the property value as well.
      </description>
      <fields>
        <field>

            while {@code !1.4} matches any JDK that is not version 1.4. Ranges are supported too:
            {@code [1.5,)} activates when the JDK is 1.5 minimum.
          </description>
        </field>
        <field>
          <name>os</name>
          <version>4.0.0+</version>
          <description>Specifies that this profile will be activated when matching operating system

///

//// tab | Linux, macOS

<div class="termy">

```console
$ source .venv/bin/activate
```

</div>

////

//// tab | Windows PowerShell

<div class="termy">

```console
$ .venv\Scripts\Activate.ps1
```

</div>

////

//// tab | Windows Bash

Make sure you create a [virtual environment](../virtual-environments.md){.internal-link target=_blank}, activate it, and then install it, for example:

```console
$ pip install python-multipart
```

///

## Import `File` and `Form` { #import-file-and-form }

            boolean reverseName = false;

            if (name == null) {
                throw new ProfileActivationException(
                        "The property name is required to activate the profile '" + profile.getId() + "'");
            }

            if (name.startsWith("!")) {
                reverseName = true;
                name = name.substring(1);
            }

To use `TestClient`, first install <a href="https://www.python-httpx.org" class="external-link" target="_blank">`httpx`</a>.

Make sure you create a [virtual environment](../virtual-environments.md){.internal-link target=_blank}, activate it, and then install it, for example:

```console
$ pip install httpx
```

///

Import `TestClient`.

Create a `TestClient` by passing your **FastAPI** application to it.

     */
    @Nonnull
    Optional<Boolean> updateSnapshots();

    /**
     * Returns the list of profiles to activate.
     *
     * @return an {@link Optional} containing the list of profile names to activate, or empty if not specified
     */
    @Nonnull
    Optional<List<String>> activatedProfiles();

    /**
     * Indicates whether Maven should suppress SNAPSHOT updates.

Make sure you create a [virtual environment](../virtual-environments.md){.internal-link target=_blank}, activate it, and then install it, for example:

```console
$ pip install python-multipart
```

///

/// note

This is supported since FastAPI version `0.113.0`. 🤓

///

For example, let's say you have 4 API endpoints (*path operations*):

* `/items/public/`
* `/items/private/`
* `/users/{user_id}/activate`
* `/items/pro/`

then you could add different permission requirements for each of them just with dependencies and sub-dependencies:

```mermaid
graph TB

current_user(["current_user"])