easyvista-python-client 0.1.0__tar.gz → 0.2.0__tar.gz

{easyvista_python_client-0.1.0 → easyvista_python_client-0.2.0}/.gitignore

@@ -9,7 +9,13 @@ venv/
 .pytest_cache/
 .mypy_cache/
 .ruff_cache/
+# Coverage data. `.coverage.*` are the per-process files pytest-cov's
+# subprocess .pth hook writes before combining; `coverage.xml` is the Codecov
+# upload artifact the CI coverage job produces, and is easy to generate locally
+# by copying that job's command.
 .coverage
+.coverage.*
+coverage.xml
 htmlcov/
 dist/
 build/
@@ -41,3 +47,9 @@ docs/easyvista-field-inventory.md
 # print real employees' names and e-mail addresses. Kept on disk so they stay
 # usable locally; never published.
 scripts/probe_*.py
+
+# Local agent instructions. Working notes for whoever drives this repo with an
+# AI assistant, not project documentation: they reference the private preprod
+# instance's behaviour and this machine's credential layout. Anything here that
+# a public reader needs belongs in CONTRIBUTING.md, docs/, or a skill instead.
+CLAUDE.md

{easyvista_python_client-0.1.0 → easyvista_python_client-0.2.0}/.pre-commit-config.yaml

@@ -1,3 +1,10 @@
+# The coverage hook below is `stages: [pre-push]`, and pre-commit only installs
+# the hook types it is told about -- so without this line `pre-commit install`
+# writes .git/hooks/pre-commit alone and the coverage gate is configured but
+# never fires. Anyone who ran `pre-commit install` before this line existed has
+# no pre-push hook and must re-run it (pre-commit install --install-hooks).
+default_install_hook_types: [pre-commit, pre-push]
+
 repos:
   - repo: https://github.com/astral-sh/ruff-pre-commit
     rev: v0.16.0
@@ -77,3 +84,27 @@ repos:
         # third entry.
         files: ^easyvista_python_client/_sync/(_concurrency\.py|tests/test_concurrency\.py)$
         pass_filenames: false
+      # The local half of the coverage gate in .github/workflows/ci.yml, so an
+      # under-covered branch is caught before the push rather than by CI after
+      # it. pre-push, not pre-commit: it runs the whole unit suite, which is far
+      # too slow to sit in front of every commit.
+      #
+      # The pytest command lives in the script rather than in `entry` here, and
+      # that indirection is load-bearing rather than tidiness. This hook has to
+      # run in the environment where `pip install -e ".[dev]"` happened --
+      # measuring a package that is not the one under test is meaningless -- so
+      # the tempting spelling is `language: system` with `entry: python -m
+      # pytest ...`, as glpi_python_client uses. On this machine that resolves
+      # the bare `python` to the Microsoft Store stub and the hook dies with
+      # exit 9009 before pytest is ever reached (verified). `language: python`
+      # instead, for the reason the two hooks above give: pre-commit builds the
+      # hook a managed venv from the interpreter that ran pre-commit, never from
+      # PATH. The script then locates the project's own interpreter and
+      # delegates to it. It imports only the stdlib, hence no
+      # additional_dependencies.
+      - id: pytest-coverage
+        name: pytest with coverage (>=95%)
+        entry: python scripts/run_coverage_gate.py
+        language: python
+        pass_filenames: false
+        stages: [pre-push]