```
.
├── Dockerfile
├── main.py
└── requirements.txt
```

Then you would just have to change the corresponding paths to copy the file inside the `Dockerfile`:

```{ .dockerfile .annotate hl_lines="10  13" }
FROM python:3.14

WORKDIR /code

COPY ./requirements.txt /code/requirements.txt

RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt

# (1)!
COPY ./main.py /code/

# (2)!

      .Builder()
      .addInterceptor(CompressionInterceptor(Zstd))
      .build()

  sendRequest("https://developers.facebook.com/docs/", client)
  sendRequest("https://www.facebook.com/robots.txt", client)
  sendRequest("https://www.instagram.com/robots.txt", client)
}

private fun sendRequest(
  url: String,
  client: OkHttpClient,
) {
  val req = Request.Builder().url(url).build()

  client.newCall(req).execute().use {

        bash -c 'clang-format-12 --style=Google {} | git diff --no-index {} -' \
        | tee $BATS_TEST_TMPDIR/needs_help.txt
    echo "You can use clang-format --style=Google -i <file> to apply changes to a file."
    [[ ! -s $BATS_TEST_TMPDIR/needs_help.txt ]]
}

# Note: this is excluded on the full code base, since any submitted code must
# have passed Google's internal style guidelines.

Available dictionary types:
- `stopwords.txt` - Words to exclude from indexing
- `stemmer_override.txt` - Custom stemming rules
- `protwords.txt` - Protected words (no stemming)
- `mapping.txt` - Character/token mappings

**Example directory structure:**
```
dictionary/
└── sv/
    ├── stopwords.txt
    ├── stemmer_override.txt
    └── protwords.txt
```

## Important Notes

.
├── Dockerfile
├── main.py
└── requirements.txt
```

Então você só teria que alterar os caminhos correspondentes para copiar o arquivo dentro do `Dockerfile`:

```{ .dockerfile .annotate hl_lines="10  13" }
FROM python:3.14

WORKDIR /code

COPY ./requirements.txt /code/requirements.txt

RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt

# (1)!
COPY ./main.py /code/

# (2)!

     * </p>
     *
     * @param rootDir the root directory (must not be {@literal null})
     * @param baseDirectory the base directory

        FileSource source = new FileSource(txtFile);

        try (InputStream is = source.getInputStream();
                Scanner scanner = new Scanner(is)) {

            assertEquals("Hello World!", scanner.nextLine());
        }
    }

    @Test
    void testGetLocation() {
        File txtFile = new File("target/test-classes/source.txt");

#  Usually these files are written by a python script from a template
#  before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec

# Installer logs
pip-log.txt
pip-delete-this-directory.txt

# Unit test / coverage reports
htmlcov/
.tox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
.hypothesis/
.pytest_cache/

# Translations
*.mo
*.pot

tasks.register<PreparePatchRelease>("preparePatchRelease") {
    group = "Versioning"
    description = "Prepares the repository for a patch release: bumps version.txt, updates released-versions.json, and clears accepted API changes."
    versionFile = layout.projectDirectory.file("version.txt")
    releasedVersionsFile = releasedVersionsFile()
    dependsOn(":architecture-test:cleanAcceptedApiChanges")

예를 들어, 앱에서 `0.112.0` 버전을 사용하고 있다고 가정해 보겠습니다.

`requirements.txt` 파일을 사용한다면 다음과 같이 버전을 지정할 수 있습니다:

```txt
fastapi[standard]==0.112.0
```

이는 정확히 `0.112.0` 버전을 사용한다는 의미입니다.

또는 다음과 같이 고정할 수도 있습니다:

```txt
fastapi[standard]>=0.112.0,<0.113.0
```

이는 `0.112.0` 이상이면서 `0.113.0` 미만의 버전을 사용한다는 의미입니다. 예를 들어 `0.112.2` 버전도 허용됩니다.