doeff-hy-pytest 0.5.0__tar.gz

doeff_hy_pytest-0.5.0/.gitignore

@@ -0,0 +1,142 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+# macOS debug symbols for the compiled extension above: build output that
+# embeds the builder's absolute paths, so it must not be distributed either.
+*.dSYM/
+.Python
+env/
+venv/
+.venv/
+ENV/
+env.bak/
+venv.bak/
+.env
+.env.*
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Testing
+.pytest_cache/
+.coverage
+.coverage.*
+coverage.xml
+*.cover
+.hypothesis/
+htmlcov/
+.tox/
+
+# IDE
+# Generated by Eclipse buildship and machine-specific: embeds the local Java home
+# and toolchain paths. The gradle build does not read it.
+ide-plugins/pycharm/.settings/org.eclipse.buildship.core.prefs
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+.DS_Store
+
+# UV
+!uv.lock
+.venv/
+
+# Ruff
+.ruff_cache/
+
+# MyPy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Generated logs, traces, and local databases
+.doeff-lint.jsonl
+.doeff-flow/
+*.jsonl
+# 旧い版の coordinator の置き場の log(版上げの下見の検 test_deployed_state_upgrade.hy が読む fixture — 生成された log ではない)
+!packages/doeff-cluster/tests/fixtures/coordinator_state_*/wal/wal.jsonl
+# codex の app-server の実物の行を録った物(行の分類の検 packages/doeff-codex/tests/test_lines.hy が読む fixture — 生成された log ではない)
+!packages/doeff-codex/tests/recorded/codex-*/*.jsonl
+*.db
+*.db-journal
+*.db-shm
+*.db-wal
+*.sqlite
+*.sqlite-journal
+*.sqlite-shm
+*.sqlite-wal
+*.sqlite3
+*.sqlite3-journal
+*.sqlite3-shm
+*.sqlite3-wal
+None
+Untitled
+
+# Local agent and browser automation state
+.agent-home/
+.playwright-mcp/
+.claude/settings.local.json
+.claude/skills/install-vscode-plugin/
+.agents/skills/install-vscode-plugin/
+
+# Accidental desktop helper bundle captured at repository root
+/server.js
+
+# Rust build artifacts
+rust/**/target/
+packages/**/target/
+
+# Local deploy keys
+proboscis_doeff_deploy
+proboscis_doeff_deploy.pub
+
+# Worktrees and orchestration
+.git-worktrees/
+.orch/
+.sisyphus/
+VAULT
+
+# Override global gitignore for examples
+!examples/
+ORCH_PROMPT.md
+.worktrees/
+
+# Local workspace artifacts
+# Repo-root scratch directory only. A `python/` directory inside a package
+# (e.g. packages/doeff-indexer/python/) is NOT covered by this rule.
+/python/
+
+
+# 設計記録は repo に入れる — global の除外(`artifacts` の dir・`*.html`・`*.svg`)を打ち消す
+# (打ち消しは dir を先に戻さないと中身に効かない)
+!docs/design/*/artifacts/
+!docs/design/**
+# 書き込みロックだけは入れない(道具が作る一時 file — 打ち消しの後に置く)
+docs/design/*/.records.lock
+
+# Repository-owned Zenn article visuals (override global image ignores)
+!/images/zenn-use-cases-v0/*.png
+# 記事が参照する採用画像は generated/ の下に在る(上の行は直下だけに効き、2026-09-16 の 47 枚は入らなかった)
+!/images/zenn-use-cases-v0/generated/
+!/images/zenn-use-cases-v0/generated/*.png
+# 手で書いた図の正本(global の `*.svg` の除外を打ち消す)
+!/publications/zenn-use-cases-v0/visuals/*.svg

doeff_hy_pytest-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 proboscis contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

doeff_hy_pytest-0.5.0/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.5
+Name: doeff-hy-pytest
+Version: 0.5.0
+Summary: pytest plugin for doeff-hy tests: a Python 3.14 fix for Hy and optional per-test time limits
+Project-URL: Homepage, https://github.com/proboscis/doeff/tree/main/packages/doeff-hy-pytest
+Project-URL: Repository, https://github.com/proboscis/doeff
+Project-URL: Issues, https://github.com/proboscis/doeff/issues
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# doeff-hy-pytest
+
+The pytest plugin for tests written with
+[doeff-hy](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy).
+
+**This README is for** developers who run pytest on Hy code that uses doeff. After
+reading it you know what the plugin does without any setting, and how to turn on its
+optional time limits for tests.
+
+## What it does
+
+pytest loads the plugin by itself (entry point `pytest11`, name `doeff_hy`). It does
+two things:
+
+| Job | When it acts | Setting needed |
+| --- | --- | --- |
+| Fixes a Hy problem on Python 3.14 | At pytest start-up, before any conftest imports Hy | None |
+| Time limits for Hy tests | During each test in a `.hy` file | Yes; off by default |
+
+**The Python 3.14 fix.** Hy replaces `ast.unparse`. On Python 3.14, when pytest reads
+fixture annotations as strings, that replacement recurses without end. The plugin
+installs a corrected replacement (`doeff_hy.ast_unparse.install()`) as soon as pytest
+starts, so it is in place even if a conftest or another plugin imports Hy first.
+
+**Why this is a separate package.** pytest marks every module of a distribution that
+declares a `pytest11` entry point for assertion rewriting. If doeff-hy itself declared
+the entry point, pytest would try to rewrite doeff-hy's `.hy` files as Python and the
+import would fail with a `SyntaxError`. This package contains no `.hy` files, so the
+mark is harmless here.
+
+The plugin does **not** collect `.hy` test files. The doeff-hy README shows the
+`conftest.py` hook that collects them:
+[Testing with deftest](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy#testing-with-deftest).
+
+## Installation
+
+doeff-hy depends on this package, so it is already installed when doeff or doeff-hy
+is:
+
+```bash
+pip install doeff      # installs doeff-hy and doeff-hy-pytest
+```
+
+You do not list it yourself. The exception: if you install doeff-hy from a git
+revision with uv, add a `[tool.uv.sources]` entry for doeff-hy-pytest from the same
+revision.
+
+To check that pytest loaded it, look for `doeff-hy-pytest` in the `plugins:` line of
+`pytest` output, or in the plugins that `pytest -VV` lists:
+
+```bash run
+pytest -VV   # doeff-hy-pytest
+```
+
+## Time limits for Hy tests
+
+Tests that run programs against in-memory or scripted handlers should be fast. The
+limits tell you when one of them becomes slow. They apply only to tests defined in
+`.hy` files (`deftest` and plain test functions in the same file); Python test files
+are not measured. With none of the three limits set, the plugin measures nothing.
+
+### The three limits
+
+| Setting | What it limits | Unit | How it is measured |
+| --- | --- | --- | --- |
+| `doeff_test_call_budget_steps` | Running one test (pytest's `call` phase; fixture setup and teardown are not included) | doeff-vm steps (a positive integer, or `default` = 100,000) | Steps the VM executed. The count does not depend on machine load; CPU seconds are reported but not judged |
+| `doeff_test_call_budget_by_marker` | Running one test that carries a given pytest mark | Wall-clock seconds, one line per mark: `mark=seconds` | For tests that do real I/O (child processes, sockets), whose cost does not show up as VM steps. A test that matches a line is judged by seconds even when a step limit is set; if several lines match, the longest limit applies |
+| `doeff_test_collect_budget_seconds` | Importing one `.hy` test file | CPU seconds | Only when the file is imported through the `pytest_doeff_import_hy_module` hook, which the collector of [doeff-adr](https://github.com/proboscis/doeff/tree/main/packages/doeff-adr) calls. With the plain `conftest.py` collector from the doeff-hy README, nothing is measured |
+
+A test that matches no `by_marker` line is judged by steps if a step limit is set, and
+is not measured otherwise. A test that executes 0 steps (it only reads data and never
+runs the VM) is within the limit.
+
+Measured time excludes work that is not the test's own cost: compiling source to
+bytecode when no cache exists, the first import of another module (a one-time cost of
+a shared dependency), and garbage collection. Each is subtracted on the same clock
+that is being judged.
+
+### What happens when a test goes over
+
+| Setting | Values |
+| --- | --- |
+| `doeff_test_budget_mode` | `report` (default): warn and list the slow tests at the end. `fail`: the slow test fails |
+| `doeff_test_budget_registry` | Directories (relative to the pytest rootdir, one per line) that list tests allowed to go over. One file per test: `<first 12 hex chars of sha256(key)>.txt`; line 1 is the key (the pytest node id, or the file path relative to rootdir for the collection limit), the following lines give the reason. When a test goes over, the message names the file to add in the first directory |
+
+In `fail` mode, a listed test that finishes in at most half of its limit also fails,
+as a stale entry, and the message names the file to delete. Between half the limit and
+the limit, the summary only reports that the entry can be removed.
+
+### Example
+
+```toml
+[tool.pytest.ini_options]
+doeff_test_call_budget_steps = "default"
+doeff_test_call_budget_by_marker = ["real_world=10"]
+doeff_test_collect_budget_seconds = 1.0
+doeff_test_budget_mode = "fail"
+doeff_test_budget_registry = ["tests/over-budget"]
+```
+
+With this configuration, each Hy test may run 100,000 VM steps; a test marked
+`real_world` may take 10 seconds of wall-clock time instead; a test over its limit
+fails unless `tests/over-budget` lists it.
+
+### More settings
+
+| Setting or API | What it does |
+| --- | --- |
+| `step_budget_multiplier` | While a step-limited test runs, the scheduler stops it once it reaches *limit × multiplier* steps (default 20), so a test that never finishes fails instead of hanging |
+| `doeff_test_call_steps_counted` | `call` (default): count all steps of the test. `world-running`: for tests that run a simulated world recorded in `doeff_core_effects.world_phases`, count only the steps of the world's running phase |
+| `doeff_hy_pytest.budget.declare_step_budget(test, steps, reason)` | Gives one test its own step limit with a one-line reason, next to the test's definition. Over the declared value fails; at most half of it fails as stale |
+| `--doeff-python-calls` | Command-line flag. Counts Python calls (`sys.monitoring` CALL events) during tests that declared a step limit, and prints one summary line. Reports only; never fails a test |
+
+The step limits need a doeff-vm build that exposes step counts
+(`doeff_vm.doeff_vm.vm_work_counts`). If it is missing, pytest stops at start-up with
+a `UsageError` instead of silently falling back to seconds.
+
+### Output
+
+With `-v`, the summary prints one line per measured test: steps, handler calls, and
+CPU seconds. Use these numbers to pick a step limit.
+
+The report and failure messages are currently written in Japanese.
+
+## How it fits with the other doeff packages
+
+doeff is published as five core packages. `pip install doeff` installs all of them.
+
+| Package | Role |
+| --- | --- |
+| [doeff](https://github.com/proboscis/doeff) | The Python API: `@do`, handler installers, `run`, the `doeff` CLI |
+| [doeff-vm](https://github.com/proboscis/doeff/tree/main/packages/doeff-vm) | The Rust VM that executes programs |
+| [doeff-core-effects](https://github.com/proboscis/doeff/tree/main/packages/doeff-core-effects) | The standard effects and their handlers |
+| [doeff-hy](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy) | Macros for writing doeff code in Hy, a Lisp that compiles to Python |
+| **doeff-hy-pytest** | This package: the pytest plugin for tests written with doeff-hy |
+
+Arrows point from a package to a package it depends on:
+
+```text
+doeff ──► doeff-vm
+  │
+  └─────► doeff-core-effects ──► doeff-hy ──► doeff-hy-pytest
+```
+
+doeff-hy also depends on doeff and doeff-core-effects, so the five packages are
+released together with matching versions. doeff-hy-pytest declares no dependencies of
+its own; it imports doeff-hy, which is always installed alongside it.
+
+## License
+
+MIT. See [LICENSE](https://github.com/proboscis/doeff/blob/main/LICENSE).

doeff_hy_pytest-0.5.0/README.md

@@ -0,0 +1,151 @@
+# doeff-hy-pytest
+
+The pytest plugin for tests written with
+[doeff-hy](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy).
+
+**This README is for** developers who run pytest on Hy code that uses doeff. After
+reading it you know what the plugin does without any setting, and how to turn on its
+optional time limits for tests.
+
+## What it does
+
+pytest loads the plugin by itself (entry point `pytest11`, name `doeff_hy`). It does
+two things:
+
+| Job | When it acts | Setting needed |
+| --- | --- | --- |
+| Fixes a Hy problem on Python 3.14 | At pytest start-up, before any conftest imports Hy | None |
+| Time limits for Hy tests | During each test in a `.hy` file | Yes; off by default |
+
+**The Python 3.14 fix.** Hy replaces `ast.unparse`. On Python 3.14, when pytest reads
+fixture annotations as strings, that replacement recurses without end. The plugin
+installs a corrected replacement (`doeff_hy.ast_unparse.install()`) as soon as pytest
+starts, so it is in place even if a conftest or another plugin imports Hy first.
+
+**Why this is a separate package.** pytest marks every module of a distribution that
+declares a `pytest11` entry point for assertion rewriting. If doeff-hy itself declared
+the entry point, pytest would try to rewrite doeff-hy's `.hy` files as Python and the
+import would fail with a `SyntaxError`. This package contains no `.hy` files, so the
+mark is harmless here.
+
+The plugin does **not** collect `.hy` test files. The doeff-hy README shows the
+`conftest.py` hook that collects them:
+[Testing with deftest](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy#testing-with-deftest).
+
+## Installation
+
+doeff-hy depends on this package, so it is already installed when doeff or doeff-hy
+is:
+
+```bash
+pip install doeff      # installs doeff-hy and doeff-hy-pytest
+```
+
+You do not list it yourself. The exception: if you install doeff-hy from a git
+revision with uv, add a `[tool.uv.sources]` entry for doeff-hy-pytest from the same
+revision.
+
+To check that pytest loaded it, look for `doeff-hy-pytest` in the `plugins:` line of
+`pytest` output, or in the plugins that `pytest -VV` lists:
+
+```bash run
+pytest -VV   # doeff-hy-pytest
+```
+
+## Time limits for Hy tests
+
+Tests that run programs against in-memory or scripted handlers should be fast. The
+limits tell you when one of them becomes slow. They apply only to tests defined in
+`.hy` files (`deftest` and plain test functions in the same file); Python test files
+are not measured. With none of the three limits set, the plugin measures nothing.
+
+### The three limits
+
+| Setting | What it limits | Unit | How it is measured |
+| --- | --- | --- | --- |
+| `doeff_test_call_budget_steps` | Running one test (pytest's `call` phase; fixture setup and teardown are not included) | doeff-vm steps (a positive integer, or `default` = 100,000) | Steps the VM executed. The count does not depend on machine load; CPU seconds are reported but not judged |
+| `doeff_test_call_budget_by_marker` | Running one test that carries a given pytest mark | Wall-clock seconds, one line per mark: `mark=seconds` | For tests that do real I/O (child processes, sockets), whose cost does not show up as VM steps. A test that matches a line is judged by seconds even when a step limit is set; if several lines match, the longest limit applies |
+| `doeff_test_collect_budget_seconds` | Importing one `.hy` test file | CPU seconds | Only when the file is imported through the `pytest_doeff_import_hy_module` hook, which the collector of [doeff-adr](https://github.com/proboscis/doeff/tree/main/packages/doeff-adr) calls. With the plain `conftest.py` collector from the doeff-hy README, nothing is measured |
+
+A test that matches no `by_marker` line is judged by steps if a step limit is set, and
+is not measured otherwise. A test that executes 0 steps (it only reads data and never
+runs the VM) is within the limit.
+
+Measured time excludes work that is not the test's own cost: compiling source to
+bytecode when no cache exists, the first import of another module (a one-time cost of
+a shared dependency), and garbage collection. Each is subtracted on the same clock
+that is being judged.
+
+### What happens when a test goes over
+
+| Setting | Values |
+| --- | --- |
+| `doeff_test_budget_mode` | `report` (default): warn and list the slow tests at the end. `fail`: the slow test fails |
+| `doeff_test_budget_registry` | Directories (relative to the pytest rootdir, one per line) that list tests allowed to go over. One file per test: `<first 12 hex chars of sha256(key)>.txt`; line 1 is the key (the pytest node id, or the file path relative to rootdir for the collection limit), the following lines give the reason. When a test goes over, the message names the file to add in the first directory |
+
+In `fail` mode, a listed test that finishes in at most half of its limit also fails,
+as a stale entry, and the message names the file to delete. Between half the limit and
+the limit, the summary only reports that the entry can be removed.
+
+### Example
+
+```toml
+[tool.pytest.ini_options]
+doeff_test_call_budget_steps = "default"
+doeff_test_call_budget_by_marker = ["real_world=10"]
+doeff_test_collect_budget_seconds = 1.0
+doeff_test_budget_mode = "fail"
+doeff_test_budget_registry = ["tests/over-budget"]
+```
+
+With this configuration, each Hy test may run 100,000 VM steps; a test marked
+`real_world` may take 10 seconds of wall-clock time instead; a test over its limit
+fails unless `tests/over-budget` lists it.
+
+### More settings
+
+| Setting or API | What it does |
+| --- | --- |
+| `step_budget_multiplier` | While a step-limited test runs, the scheduler stops it once it reaches *limit × multiplier* steps (default 20), so a test that never finishes fails instead of hanging |
+| `doeff_test_call_steps_counted` | `call` (default): count all steps of the test. `world-running`: for tests that run a simulated world recorded in `doeff_core_effects.world_phases`, count only the steps of the world's running phase |
+| `doeff_hy_pytest.budget.declare_step_budget(test, steps, reason)` | Gives one test its own step limit with a one-line reason, next to the test's definition. Over the declared value fails; at most half of it fails as stale |
+| `--doeff-python-calls` | Command-line flag. Counts Python calls (`sys.monitoring` CALL events) during tests that declared a step limit, and prints one summary line. Reports only; never fails a test |
+
+The step limits need a doeff-vm build that exposes step counts
+(`doeff_vm.doeff_vm.vm_work_counts`). If it is missing, pytest stops at start-up with
+a `UsageError` instead of silently falling back to seconds.
+
+### Output
+
+With `-v`, the summary prints one line per measured test: steps, handler calls, and
+CPU seconds. Use these numbers to pick a step limit.
+
+The report and failure messages are currently written in Japanese.
+
+## How it fits with the other doeff packages
+
+doeff is published as five core packages. `pip install doeff` installs all of them.
+
+| Package | Role |
+| --- | --- |
+| [doeff](https://github.com/proboscis/doeff) | The Python API: `@do`, handler installers, `run`, the `doeff` CLI |
+| [doeff-vm](https://github.com/proboscis/doeff/tree/main/packages/doeff-vm) | The Rust VM that executes programs |
+| [doeff-core-effects](https://github.com/proboscis/doeff/tree/main/packages/doeff-core-effects) | The standard effects and their handlers |
+| [doeff-hy](https://github.com/proboscis/doeff/tree/main/packages/doeff-hy) | Macros for writing doeff code in Hy, a Lisp that compiles to Python |
+| **doeff-hy-pytest** | This package: the pytest plugin for tests written with doeff-hy |
+
+Arrows point from a package to a package it depends on:
+
+```text
+doeff ──► doeff-vm
+  │
+  └─────► doeff-core-effects ──► doeff-hy ──► doeff-hy-pytest
+```
+
+doeff-hy also depends on doeff and doeff-core-effects, so the five packages are
+released together with matching versions. doeff-hy-pytest declares no dependencies of
+its own; it imports doeff-hy, which is always installed alongside it.
+
+## License
+
+MIT. See [LICENSE](https://github.com/proboscis/doeff/blob/main/LICENSE).

doeff_hy_pytest-0.5.0/pyproject.toml

@@ -0,0 +1,30 @@
+[build-system]
+# license の SPDX の式と license-files(PEP 639)を既定で core metadata に書くのは hatchling 1.27 から(既定の版 2.4)。
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "doeff-hy-pytest"
+version = "0.5.0"
+description = "pytest plugin for doeff-hy tests: a Python 3.14 fix for Hy and optional per-test time limits"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "MIT"
+license-files = ["LICENSE"]
+# 依存を宣言しない: この plugin は doeff-hy に引かれて入る(doeff-hy → doeff-hy-pytest の向きだけ)。
+# 当て物の本体は doeff_hy.ast_unparse にあり、plugin はそれを import して当てるだけ。
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/proboscis/doeff/tree/main/packages/doeff-hy-pytest"
+Repository = "https://github.com/proboscis/doeff"
+Issues = "https://github.com/proboscis/doeff/issues"
+
+# pytest は pytest11 の entry point を持つ配布物の**全 module** に assert の書き換えの印を付ける。doeff-hy 自身がこの
+# entry point を持つと doeff_hy の .hy(macros.hy など)まで Python として書き換えようとして import が落ちる(wheel で
+# 入れた repo だけ — editable の install では印が付かない)。だから plugin は .hy を持たないこの配布物に置く。
+[project.entry-points.pytest11]
+doeff_hy = "doeff_hy_pytest"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/doeff_hy_pytest"]

doeff_hy_pytest-0.5.0/src/doeff_hy_pytest/__init__.py

@@ -0,0 +1,25 @@
+"""doeff-hy の pytest plugin(entry point `pytest11` の名 `doeff_hy`)。
+
+pytest は起動時に plugin と conftest を読み、fixture の注記を Python 3.14 では
+`annotation_format=Format.STRING` で読む。Hy がそれより前に(他の plugin や conftest から)
+import されていると、Hy の `ast.unparse` の差し替えがそこで止まらない再帰になる
+(doeff_hy/ast_unparse.py)。`import doeff_hy` を待たず、pytest の起動の時点で置き換えるための plugin。
+
+もう 1 つの役目は Hy の検の時間の上限(doeff_hy_pytest/budget.py — 設定が無ければ何もしない)。hook は
+この module から輸出して、entry point の 1 つ(`doeff_hy`)のまま載せる。
+
+この module が doeff-hy とは別の配布物にある理由は pyproject.toml の註(pytest の assert の書き換えの印が
+配布物の全 module に付き、doeff_hy の .hy を壊す)。
+"""
+
+from doeff_hy.ast_unparse import install
+
+from doeff_hy_pytest.budget import pytest_addoption as pytest_addoption
+from doeff_hy_pytest.budget import pytest_configure as pytest_configure
+from doeff_hy_pytest.budget import pytest_doeff_import_hy_module as pytest_doeff_import_hy_module
+from doeff_hy_pytest.budget import pytest_runtest_call as pytest_runtest_call
+from doeff_hy_pytest.budget import pytest_runtest_makereport as pytest_runtest_makereport
+from doeff_hy_pytest.budget import pytest_terminal_summary as pytest_terminal_summary
+from doeff_hy_pytest.budget import pytest_unconfigure as pytest_unconfigure
+
+install()