@elaraai/create-e3 1.0.69 → 1.0.71

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elaraai/create-e3",
-  "version": "1.0.69",
+  "version": "1.0.71",
   "description": "Scaffold a new e3 project (BSL-1.1, Node + Python, durable execution): npm create @elaraai/e3",
   "type": "module",
   "bin": {

package/templates/e3/_packages/python/src/__PACKAGE_NAME__/example.py

@@ -1,18 +1,19 @@
 """An example Python platform function owned by the ``__PACKAGE_NAME__`` package.
 
 Platform functions let East call NATIVE Python (numpy, pandas, scikit-learn, …)
-that East itself can't express. The ``@platform_function`` is bound to East by
-its dotted ``"__PACKAGE_NAME__.<fn>"`` name, which the TypeScript declaration in
-``src/packages/__PACKAGE_NAME__.ts`` mirrors exactly — keep the two in lockstep.
-Add native dependencies to this package's ``pyproject.toml`` and import them
+that East itself can't express. The ``@East.platform_function`` is bound to
+East by its dotted ``"__PACKAGE_NAME__.<fn>"`` name, which the TypeScript
+declaration in ``src/packages/__PACKAGE_NAME__.ts`` mirrors exactly — keep the
+two in lockstep. A python-authored East body (``functions.py``) needs no
+declaration: the decorated function is callable inside one directly. Add
+native dependencies to this package's ``pyproject.toml`` and import them
 inside the body.
 """
 
-from east.runtime.platform import platform_function, platform_functions
-from east.types.types import ArrayType, FloatType
+from east import ArrayType, East, FloatType
 
 
-@platform_function(
+@East.platform_function(
     inputs=[ArrayType(FloatType)],
     output=FloatType,
     name="__PACKAGE_NAME__.example",
@@ -24,4 +25,4 @@ def example(values):
 
 
 # The platform functions defined in THIS module, in definition order.
-example_impl = platform_functions(__name__)
+example_impl = East.platform_functions(__name__)

package/templates/e3/platform_module/example.py

@@ -1,10 +1,12 @@
 """An example project-owned Python platform function — replace it with your own.
 
 Platform functions let East call NATIVE Python (numpy, pandas, scikit-learn, …)
-that East itself can't express. The ``@platform_function`` is bound to East by
-its dotted ``"<project>.<fn>"`` name, which the TypeScript declaration in
-``src/platform_module.ts`` mirrors exactly — keep the two in lockstep. Add
-native dependencies to ``pyproject.toml`` and import them inside the body.
+that East itself can't express. The ``@East.platform_function`` is bound to
+East by its dotted ``"<project>.<fn>"`` name, which the TypeScript declaration
+in ``src/platform_module.ts`` mirrors exactly — keep the two in lockstep. A
+python-authored East body needs no declaration: the decorated function is
+callable inside one directly. Add native dependencies to ``pyproject.toml``
+and import them inside the body.
 
 This module ends by collecting its functions into ``example_impl`` (the
 canonical east-py idiom — ``platform_functions`` keys the registry on each
@@ -12,11 +14,10 @@ function's ``__module__``), which ``__init__.py`` spreads into the package's
 top-level ``platform`` list.
 """
 
-from east.runtime.platform import platform_function, platform_functions
-from east.types.types import ArrayType, FloatType
+from east import ArrayType, East, FloatType
 
 
-@platform_function(
+@East.platform_function(
     inputs=[ArrayType(FloatType)],
     output=FloatType,
     name="__PROJECT_NAME__.example_python",
@@ -28,4 +29,4 @@ def example_python(values):
 
 
 # The platform functions defined in THIS module, in definition order.
-example_impl = platform_functions(__name__)
+example_impl = East.platform_functions(__name__)

package/templates/e3/pyproject.platform.toml

@@ -13,6 +13,22 @@ dependencies = [
   "pytest-subtests",
 ]
 
+# East diagnostics (`east-py lint`, the flake8 and pylsp plugins, and
+# `east-py lsp`) read this section.
+#
+# `check` turns on the BUILD tier, which type-checks your East functions by
+# building them — the only way to type-check an East body, since East's checker
+# is the builder. It is off here because building means IMPORTING the module,
+# so your editor would execute this project's code on every save. Turn it on
+# once your module-level code is safe to run on save, or skips its work when it
+# sees `EAST_CHECK`:
+#
+#   check = true
+#
+# `east-py check src/` on the command line always works and ignores this.
+[tool.east-py]
+check = false
+
 # Packaging block — without it `uv sync` would not install this project's own
 # code, so `east-py run -p platform_module` could not import it. Matches the
 # repo's pure-Python packages (east-py-std/io/cli). This variant of

package/templates/e3/pyproject.toml

@@ -12,3 +12,19 @@ dependencies = [
   "pytest",
   "pytest-subtests",
 ]
+
+# East diagnostics (`east-py lint`, the flake8 and pylsp plugins, and
+# `east-py lsp`) read this section.
+#
+# `check` turns on the BUILD tier, which type-checks your East functions by
+# building them — the only way to type-check an East body, since East's checker
+# is the builder. It is off here because building means IMPORTING the module,
+# so your editor would execute this project's code on every save. Turn it on
+# once your module-level code is safe to run on save, or skips its work when it
+# sees `EAST_CHECK`:
+#
+#   check = true
+#
+# `east-py check src/` on the command line always works and ignores this.
+[tool.east-py]
+check = false