python-ddd-framework 0.7.2__tar.gz → 0.7.3__tar.gz

{python_ddd_framework-0.7.2 → python_ddd_framework-0.7.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-ddd-framework
-Version: 0.7.2
+Version: 0.7.3
 Summary: Modular DDD application framework with project CLI and bundled templates
 License-Expression: LicenseRef-Proprietary
 License-File: LICENSE
@@ -169,6 +169,8 @@ Open **http://127.0.0.1:8000/docs**. Use the generated `identity.seed_admin_user
 
 The empty `orders` skeleton contributes no business routes. The independent [order-management example](examples/order_management/README.md) supplies `/api/orders`, approval and queued approval, file transfer, and an authenticated WebSocket at `/ws/orders`; use its initializer when you want to explore those capabilities.
 
+For C++ computation, the independent [native integration example](examples/native_integration/README.md) demonstrates an installed nanobind package, typed application-service consumption, cancellation cleanup, source rebuilds, and artifact delivery. It is outside the runtime wheel and does not change the CLI or default templates. Verified platforms and remaining limits are recorded in [status](docs/status.md#c-原生接入样例).
+
 The default business API prefix is `/api`. Liveness and readiness are exposed at `/health/live` and `/health/ready`; readiness describes application lifecycle state, not continuous database or Redis health.
 
 ## CLI reference
@@ -318,6 +320,12 @@ Function calls avoid regenerating DI wrappers, empty extension chains skip unnec
 
 Public APIs, DI scopes, authorization, validation, Unit of Work, exception and cancellation behavior are unchanged. No application-code, configuration or data migration is required. Follow the existing [upgrade procedure](#upgrading); validation evidence and performance limits are recorded in [release status](docs/status.md#当前发布).
 
+## Native C++ integration example (0.7.3)
+
+The repository's [native integration example](examples/native_integration/README.md) demonstrates a separately installed nanobind package, Eigen computation, typed service/HTTP consumption, cancellation cleanup, and wheel/sdist and Docker delivery. Its development entry rebuilds declared native path dependencies before starting the existing Host. The example and its native binaries are maintained outside the framework runtime wheel.
+
+Existing applications need no code, configuration, dependency or data migration. Adopt the example from the source checkout when adding native computation; the CLI, default templates and framework lifecycle contracts are unchanged. Platform evidence and remaining limits are recorded in [release status](docs/status.md#当前发布).
+
 <a id="streaming-and-access-migration-07-unreleased"></a>
 
 ## Streaming and access migration (0.7)

{python_ddd_framework-0.7.2 → python_ddd_framework-0.7.3}/README.md

@@ -125,6 +125,8 @@ Open **http://127.0.0.1:8000/docs**. Use the generated `identity.seed_admin_user
 
 The empty `orders` skeleton contributes no business routes. The independent [order-management example](examples/order_management/README.md) supplies `/api/orders`, approval and queued approval, file transfer, and an authenticated WebSocket at `/ws/orders`; use its initializer when you want to explore those capabilities.
 
+For C++ computation, the independent [native integration example](examples/native_integration/README.md) demonstrates an installed nanobind package, typed application-service consumption, cancellation cleanup, source rebuilds, and artifact delivery. It is outside the runtime wheel and does not change the CLI or default templates. Verified platforms and remaining limits are recorded in [status](docs/status.md#c-原生接入样例).
+
 The default business API prefix is `/api`. Liveness and readiness are exposed at `/health/live` and `/health/ready`; readiness describes application lifecycle state, not continuous database or Redis health.
 
 ## CLI reference
@@ -274,6 +276,12 @@ Function calls avoid regenerating DI wrappers, empty extension chains skip unnec
 
 Public APIs, DI scopes, authorization, validation, Unit of Work, exception and cancellation behavior are unchanged. No application-code, configuration or data migration is required. Follow the existing [upgrade procedure](#upgrading); validation evidence and performance limits are recorded in [release status](docs/status.md#当前发布).
 
+## Native C++ integration example (0.7.3)
+
+The repository's [native integration example](examples/native_integration/README.md) demonstrates a separately installed nanobind package, Eigen computation, typed service/HTTP consumption, cancellation cleanup, and wheel/sdist and Docker delivery. Its development entry rebuilds declared native path dependencies before starting the existing Host. The example and its native binaries are maintained outside the framework runtime wheel.
+
+Existing applications need no code, configuration, dependency or data migration. Adopt the example from the source checkout when adding native computation; the CLI, default templates and framework lifecycle contracts are unchanged. Platform evidence and remaining limits are recorded in [release status](docs/status.md#当前发布).
+
 <a id="streaming-and-access-migration-07-unreleased"></a>
 
 ## Streaming and access migration (0.7)

{python_ddd_framework-0.7.2 → python_ddd_framework-0.7.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "python-ddd-framework"
-version = "0.7.2"
+version = "0.7.3"
 description = "Modular DDD application framework with project CLI and bundled templates"
 readme = "README.md"
 license = "LicenseRef-Proprietary"

{python_ddd_framework-0.7.2 → python_ddd_framework-0.7.3}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "python-ddd-framework"
-version = "0.7.2"
+version = "0.7.3"
 description = "Modular DDD application framework with project CLI and bundled templates"
 readme = "README.md"
 license = "LicenseRef-Proprietary"