from(src) {
                eachFile {
                    // Remove top folder when unzipping, that way we get rid of Android Studio.app folder that can cause issues on Mac
                    // where MacOS would kill the Android Studio process right after start, issue: https://github.com/gradle/gradle-profiler/issues/469
                    @Suppress("SpreadOperator")

        docsTestTriggers.forEach(this::buildType)

        flakyTestQuarantineTriggers = mutableListOf()
        if (stage.stageName == StageName.READY_FOR_RELEASE) {
            listOf(Os.LINUX, Os.WINDOWS, Os.MACOS).forEach {
                val flakyTestQuarantineProject = FlakyTestQuarantineProject(model, stage, it)
                val flakyTestQuarantineProjectTrigger = FlakyTestQuarantineTrigger(model, flakyTestQuarantineProject)

  val safari12iOS = sslLabsClients.first { it.userAgent == "Safari" && it.platform == "iOS 12.3.1" }
  val safari12Osx =
    sslLabsClients.first { it.userAgent == "Safari" && it.platform == "MacOS 10.14.6 Beta" }

  val okhttp = currentOkHttp(ianaSuitesNew)

  val okHttp_4_10 = historicOkHttp("4.10")
  val okHttp_3_14 = historicOkHttp("3.14")
  val okHttp_3_13 = historicOkHttp("3.13")

### GNU/Linux and macOS

```sh
docker-compose pull
docker-compose up
```

or

```sh
docker stack deploy --compose-file docker-compose.yaml minio
```

### Windows

```sh
docker-compose.exe pull

 * [okhttp-system-keystore](https://github.com/charleskorn/okhttp-system-keystore): Use trusted certificates from the operating system keystore (Keychain on macOS, Certificate Store on Windows).
 * ⬜️ [Okio](https://github.com/square/okio/): A modern I/O API for Java.

## Managing hermetic Python

To make sure that TensorFlow's build is reproducible, behaves uniformly across
supported platforms (Linux, Windows, MacOS) and is properly isolated from
specifics of a local system, we rely on hermetic Python (see
[rules_python](https://github.com/bazelbuild/rules_python)) for all build
and test commands executed via Bazel. This means that your system Python
installation will be ignored during the build and Python interpreter itself

 * <ul>
 * <li>windows: All Windows variants</li>
 * <li>win9x: Windows 95, 98, ME, CE</li>
 * <li>winnt: Windows NT variants</li>
 * <li>unix: Unix-like systems (including Linux)</li>
 * <li>mac: macOS (including Darwin)</li>
 * <li>os/2: OS/2 variants</li>
 * <li>netware: Novell NetWare</li>
 * <li>dos: DOS variants</li>
 * <li>tandem: Tandem systems</li>
 * <li>openvms: OpenVMS</li>
 * <li>z/os: z/OS and OS/390</li>

## 环境变量

/// tip

如果您已经知道什么是"环境变量"以及如何使用它们，请随意跳到下面的下一节。

///

环境变量（也称为"env var"）是一种存在于 Python 代码之外、存在于操作系统中的变量，可以被您的 Python 代码（或其他程序）读取。

您可以在 shell 中创建和使用环境变量，而无需使用 Python：

//// tab | Linux、macOS、Windows Bash

<div class="termy">

```console
// 您可以创建一个名为 MY_NAME 的环境变量
$ export MY_NAME="Wade Wilson"

// 然后您可以与其他程序一起使用它，例如
$ echo "Hello $MY_NAME"

Hello Wade Wilson
```

</div>

These environment variables can only handle text strings, as they are external to Python and have to be compatible with other programs and the rest of the system (and even with different operating systems, as Linux, Windows, macOS).

That means that any value read in Python from an environment variable will be a `str`, and any conversion to a different type or any validation has to be done in code.

## Pydantic `Settings` { #pydantic-settings }

Essas variáveis de ambiente só conseguem lidar com strings de texto, pois são externas ao Python e precisam ser compatíveis com outros programas e com o resto do sistema (e até com diferentes sistemas operacionais, como Linux, Windows, macOS).

Isso significa que qualquer valor lido em Python a partir de uma variável de ambiente será uma `str`, e qualquer conversão para um tipo diferente ou validação precisa ser feita em código.