}

  static class MeanAndVariance {
    private final double mean;
    private final double variance;

    MeanAndVariance(double mean, double variance) {
      this.mean = mean;
      this.variance = variance;
    }

    @Override
    public int hashCode() {
      return Double.hashCode(mean) * 31 + Double.hashCode(variance);
    }
  }

  enum VarianceAlgorithm {
    DO_NOT_COMPUTE {
      @Override

  }

  static class MeanAndVariance {
    private final double mean;
    private final double variance;

    MeanAndVariance(double mean, double variance) {
      this.mean = mean;
      this.variance = variance;
    }

    @Override
    public int hashCode() {
      return Double.hashCode(mean) * 31 + Double.hashCode(variance);
    }
  }

  enum VarianceAlgorithm {
    DO_NOT_COMPUTE {
      @Override

### Do

* Ensure that the system executing your microbenchmarks has as little load as possible. Shutdown every process that can cause unnecessary
  runtime jitter. Watch the `Error` column in the benchmark results to see the run-to-run variance.
* Ensure to run enough warmup iterations to get the benchmark into a stable state. If you are unsure, don't change the defaults.
* Avoid CPU migrations by pinning your benchmarks to specific CPU cores. On Linux you can use `taskset`.

        assertTrue(
                later.minus(initial).toMillis() >= 45,
                "Elapsed time difference should be at least 45ms (accounting for some timing variance)");
    }

    @Test
    @DisplayName("MonotonicClock start time should remain constant")
    void testStartTime() throws InterruptedException {
        Instant start1 = MonotonicClock.start();

 * <p>
 * Supported OS families include:
 * <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>

      "buildId": "${maven.build.version}"
    }
  },
  "variants": [
    {
      "name": "${variant.jvmEnvironmentVariantName}ApiElements",
      "attributes": {
        "org.gradle.category": "library",
        "org.gradle.dependency.bundling": "external",
        "org.gradle.jvm.version": "8",
        "org.gradle.jvm.environment": "${variant.jvmEnvironment}",
        "org.gradle.libraryelements": "jar",

* **Consistency with dependencies**: Gradle's ecosystem and dependencies predominantly use American English

### Exceptions

Some legitimate exceptions exist where British English or other variants must be preserved:

* **Third-party APIs and libraries**: When integrating with external APIs that use different spelling conventions

```console
// Ici, nous ne définissons pas encore la variable d'environnement
$ python main.py

// Comme nous ne l'avons pas définie, nous obtenons la valeur par défaut

Hello World from Python

// Mais si nous créons d'abord une variable d'environnement
$ export MY_NAME="Wade Wilson"

// Puis que nous relançons le programme
$ python main.py

// Il peut maintenant lire la variable d'environnement

Hello Wade Wilson from Python

Cuando instalas Python, se te podría preguntar si deseas actualizar la variable de entorno `PATH`.

//// tab | Linux, macOS

Digamos que instalas Python y termina en un directorio `/opt/custompython/bin`.

Si dices que sí para actualizar la variable de entorno `PATH`, entonces el instalador añadirá `/opt/custompython/bin` a la variable de entorno `PATH`.

Podría verse así:

```plaintext

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.

You will learn more about using environment variables for handling **application settings** in the [Advanced User Guide - Settings and Environment Variables](./advanced/settings.md).

## `PATH` Environment Variable { #path-environment-variable }