- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 199 for STANDARD (0.04 sec)
-
internal/config/storageclass/storage-class.go
"github.com/minio/minio/internal/logger" "github.com/minio/pkg/v3/env" ) // Standard constants for all storage class const ( // Reduced redundancy storage class RRS = "REDUCED_REDUNDANCY" // Standard storage class STANDARD = "STANDARD" ) // Standard constats for config info storage class const ( ClassStandard = "standard" ClassRRS = "rrs" Optimize = "optimize" InlineBlock = "inline_block"
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 12 12:24:04 UTC 2024 - 12.3K bytes - Viewed (0) -
docs/de/docs/advanced/dataclasses.md
In diesem Fall können Sie einfach die Standard-`dataclasses` durch `pydantic.dataclasses` ersetzen, was einen direkten Ersatz darstellt: ```{ .python .annotate hl_lines="1 5 8-11 14-17 23-25 28" } {!../../docs_src/dataclasses/tutorial003.py!} ``` 1. Wir importieren `field` weiterhin von Standard-`dataclasses`. 2. `pydantic.dataclasses` ist ein direkter Ersatz für `dataclasses`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 4.6K bytes - Viewed (0) -
docs/en/docs/advanced/dataclasses.md
In that case, you can simply swap the standard `dataclasses` with `pydantic.dataclasses`, which is a drop-in replacement: {* ../../docs_src/dataclasses/tutorial003.py hl[1,5,8:11,14:17,23:25,28] *} 1. We still import `field` from standard `dataclasses`. 2. `pydantic.dataclasses` is a drop-in replacement for `dataclasses`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 28 10:35:06 UTC 2024 - 4K bytes - Viewed (0) -
pyproject.toml
[project.optional-dependencies] standard = [ "fastapi-cli[standard] >=0.0.5", # For the test client "httpx >=0.23.0", # For templates "jinja2 >=2.11.2", # For forms and file uploads "python-multipart >=0.0.7", # To validate email fields "email-validator >=2.0.0", # Uvicorn with uvloop "uvicorn[standard] >=0.12.0",
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Oct 22 14:19:56 UTC 2024 - 7.9K bytes - Viewed (0) -
compat/maven-plugin-api/src/main/java/org/apache/maven/plugin/Mojo.java
/** * Inject a standard <code>Maven</code> logging mechanism to allow this <code>Mojo</code> to communicate events * and feedback to the user. * * @param log a new logger * * @deprecated Use SLF4J directly */ @Deprecated void setLog(Log log); /** * Furnish access to the standard Maven logging mechanism which is managed in this base class.
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 2.9K bytes - Viewed (0) -
docs/en/docs/deployment/manually.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Aug 25 02:44:06 UTC 2024 - 7.8K bytes - Viewed (0) -
docs/en/docs/tutorial/extra-data-types.md
* The generated schema will specify that the `set` values are unique (using JSON Schema's `uniqueItems`). * `bytes`: * Standard Python `bytes`. * In requests and responses will be treated as `str`. * The generated schema will specify that it's a `str` with `binary` "format". * `Decimal`: * Standard Python `Decimal`. * In requests and responses, handled the same as a `float`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 4K bytes - Viewed (0) -
docs/de/docs/advanced/response-change-status-code.md
# Response – Statuscode ändern Sie haben wahrscheinlich schon vorher gelesen, dass Sie einen Standard-[Response-Statuscode](../tutorial/response-status-code.md){.internal-link target=_blank} festlegen können. In manchen Fällen müssen Sie jedoch einen anderen als den Standard-Statuscode zurückgeben. ## Anwendungsfall Stellen Sie sich zum Beispiel vor, Sie möchten standardmäßig den HTTP-Statuscode „OK“ `200` zurückgeben.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 1.8K bytes - Viewed (0) -
README.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Oct 31 09:13:26 UTC 2024 - 23.6K bytes - Viewed (0) -
src/README.vendor
copies of a package at different versions if the package is imported normally and vendored by the standard library. Vendored packages are internally renamed with a "vendor/" prefix to preserve the invariant that all packages have distinct paths. This is necessary to avoid compiler and linker conflicts. Adding a "vendor/" prefix also maintains the invariant that standard library packages begin with a dotless path element.
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Mon Sep 30 19:15:39 UTC 2024 - 2.4K bytes - Viewed (0)