</developers>
  <ciManagement>
    <system>GitHub Actions</system>
    <url>https://github.com/google/guava/actions</url>
  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>

 * from a Project Object Model (POM).</p>
 *
 * <p><dfn>Project Object Model</dfn> or <dfn>POM</dfn> refers to the information describing
 * all the information needed to build or consume a project. Those are usually loaded from
 * a file named {@code pom.xml} and loaded into a {@link org.apache.maven.api.model.Model Model}
 * instances.</p>
 *

The `app_name` would be `"ChimichangApp"`.

And the `items_per_user` would keep its default value of `50`.

## Settings in another module { #settings-in-another-module }

You could put those settings in another module file as you saw in [Bigger Applications - Multiple Files](../tutorial/bigger-applications.md){.internal-link target=_blank}.

For example, you could have a file `config.py` with:

 ╭─ <font color="#8AE234"><b>Python module file</b></font> ─╮
 │                      │
 │  🐍 main.py          │
 │                      │
 ╰──────────────────────╯

<font color="#3465A4">INFO    </font> Importing module <font color="#4E9A06">main</font>
<font color="#3465A4">INFO    </font> Found importable FastAPI app

{* ../../docs_src/settings/tutorial001.py hl[2,5:8,11] *}

////

//// tab | Pydantic v1

/// info

Na versão 1 do Pydantic você importaria `BaseSettings` diretamente do módulo `pydantic` em vez do módulo `pydantic_settings`.

///

{* ../../docs_src/settings/tutorial001_pv1.py hl[2,5:8,11] *}

////

/// tip | Dica

constraints.Length.message = Die Länge von {item} muss zwischen {min} und {max} liegen.
constraints.LuhnCheck.message = Die Luhn-Modulo-11-Prüfsumme von {value} ist falsch.
constraints.Mod10Check.message = Die Modulo-10-Prüfsumme von {value} ist falsch.
constraints.Mod11Check.message = Die Modulo-11-Prüfsumme von {value} ist falsch.
constraints.ModCheck.message = Die {modType}-Prüfsumme von {value} ist falsch.

constraints.Length.message = De lengte van {item} moet tussen {min} en {max} liggen.
constraints.LuhnCheck.message = De Luhn Modulo 11 checksum van {value} is onjuist.
constraints.Mod10Check.message = De Modulo 10 checksum van {value} is onjuist.
constraints.Mod11Check.message = De Modulo 11 checksum van {value} is onjuist.
constraints.ModCheck.message = De {modType} checksum van {value} is onjuist.

				"message/vnd.si.simp",
				"model/example",
				"model/iges",
				"model/mesh",
				"model/vnd.dwf",
				"model/vnd.dwfx+xps",
				"model/vnd.flatland.3dml",
				"model/vnd.gdl",
				"model/vnd.gs-gdl",
				"model/vnd.gs.gdl",
				"model/vnd.gtw",
				"model/vnd.moml+xml",
				"model/vnd.mts",
				"model/vnd.parasolid.transmit.binary",
				"model/vnd.parasolid.transmit.text",

        the `run_eagerly` property, and will correctly run using `tf.function`
        by default. Note that `Model.fit_generator`, `Model.evaluate_generator`,
        and `Model.predict_generator` are deprecated endpoints. They are
        subsumed by `Model.fit`, `Model.evaluate`, and `Model.predict` which now
        support generators and Sequences.
*   `tf.lite`
    *   Legalization for `NMS` ops in TFLite.

##### Changes

 * New: Support for `HTTP-draft-09/2.0`.
 * New: Support for `spdy/3.1`. Dropped support for `spdy/3`.
 * New: Use ALPN on Android platforms that support it (4.4+)
 * New: CacheControl model and parser.
 * New: Protocol selection in MockWebServer.
 * Fix: Route selection shouldn't use TLS modes that we know will fail.
 * Fix: Cache SPDY responses even if the response body is closed prematurely.