hocon-parser 1.8.0__tar.gz

hocon_parser-1.8.0/.github/workflows/lint.yml

@@ -0,0 +1,36 @@
+name: Lint
+
+on:
+  pull_request:
+    branches: [develop, main]
+  push:
+    branches: [develop, main]
+
+jobs:
+  ruff:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.13"
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e . --group dev
+      - run: ruff check src tests benchmarks tools
+
+  typecheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      # Pinned to the floor of requires-python so stdlib drift in newer
+      # versions can't mask a 3.11 incompatibility (mypy python_version=3.11).
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e . --group dev
+      - run: mypy

hocon_parser-1.8.0/.github/workflows/release.yml

@@ -0,0 +1,105 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions: {}
+
+jobs:
+  publish:
+    name: Publish to PyPI
+    runs-on: ubuntu-latest
+    # Least-privilege: only the publish job needs write scope (contents for
+    # the GitHub Release, id-token for PyPI Trusted Publishing). Workflow-level
+    # `permissions: {}` denies by default so future jobs added here don't
+    # inherit write access without an explicit declaration.
+    permissions:
+      contents: write
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.13"
+
+      - name: Set version from tag
+        # Idempotent: skip the rewrite if pyproject.toml is already at the
+        # tag's version, so a release-prep PR that pre-bumped the manifest
+        # doesn't break the publish (same convention as the siblings).
+        run: |
+          TAG_VERSION="${GITHUB_REF#refs/tags/v}"
+          CURRENT=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
+          if [ "$TAG_VERSION" != "$CURRENT" ]; then
+            sed -i "s/^version = \"$CURRENT\"/version = \"$TAG_VERSION\"/" pyproject.toml
+          else
+            echo "pyproject.toml already at $CURRENT — skipping bump"
+          fi
+
+      - name: Fetch conformance corpus
+        run: make testdata
+
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e . --group dev
+
+      - name: Type check
+        run: mypy
+
+      - name: Test
+        run: python -m pytest
+
+      - name: Build distributions
+        run: |
+          python -m pip install build
+          python -m build
+
+      - name: Extract CHANGELOG section for this tag
+        # Pulls the section between `## [VERSION]` and the next `## [`
+        # from CHANGELOG.md so the GitHub Release body matches what's
+        # already committed and reviewed.
+        #
+        # Uses `index($0, str) == 1` (prefix match) rather than awk regex
+        # so SemVer build metadata (`+...`) and other regex metacharacters
+        # in version strings can't break or overmatch the section header.
+        #
+        # Runs BEFORE the PyPI upload (and the GitHub Release step below)
+        # so that a missing/incorrect CHANGELOG heading fails the run
+        # without first publishing — PyPI doesn't allow re-uploading the
+        # same version, so an irreversible upload followed by a failed
+        # release step would leave a half-shipped tag.
+        run: |
+          VERSION="${GITHUB_REF#refs/tags/v}"
+          awk -v ver="$VERSION" '
+            index($0, "## [" ver "]") == 1 { flag=1; next }
+            flag && index($0, "## [") == 1 { flag=0 }
+            flag
+          ' CHANGELOG.md > /tmp/release-notes.md
+          if [ ! -s /tmp/release-notes.md ]; then
+            echo "::error::No CHANGELOG section found for v${VERSION}; aborting release so an empty body doesn't ship"
+            exit 1
+          fi
+
+      - name: Create GitHub Release
+        # Runs before the PyPI upload so a Release-creation failure doesn't
+        # leave a PyPI artifact published without a GitHub Release entry
+        # (PyPI forbids re-uploading the same version, so a retry would fail
+        # at the upload step and never reach this step again).
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ github.ref_name }}
+          name: ${{ github.ref_name }}
+          body_path: /tmp/release-notes.md
+          fail_on_unmatched_files: false
+          make_latest: true
+
+      - name: Publish to PyPI
+        # Trusted Publishing (OIDC) — no API token. Requires this repo +
+        # workflow file to be registered as a trusted publisher for the
+        # `py.hocon` project on PyPI before the first release.
+        uses: pypa/gh-action-pypi-publish@release/v1

hocon_parser-1.8.0/.github/workflows/test.yml

@@ -0,0 +1,61 @@
+name: Test
+
+on:
+  pull_request:
+    branches: [develop, main]
+  push:
+    branches: [develop, main]
+
+jobs:
+  test:
+    name: py${{ matrix.python }} / ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+        os: [ubuntu-latest]
+        include:
+          - python: "3.13"
+            os: macos-latest
+          - python: "3.13"
+            os: windows-latest
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python }}
+
+      # No cache: `make testdata` fetches the whole corpus fresh each run (a
+      # small tarball, sha-resolved via `git ls-remote`). Nothing is vendored
+      # in this repo, so a partial or stale cache can only subtract
+      # correctness — see rs.hocon's stale-fixture regression (#101) that led
+      # the siblings to drop fixture caching.
+      - name: Fetch conformance corpus
+        run: make testdata
+
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e . --group dev
+
+      - name: Test
+        run: python -m pytest
+
+      - name: Test with coverage
+        if: matrix.python == '3.13' && matrix.os == 'ubuntu-latest'
+        run: |
+          python -m pip install pytest-cov
+          python -m pytest --cov=hocon --cov-report=xml
+
+      - name: Upload coverage to Codecov
+        if: matrix.python == '3.13' && matrix.os == 'ubuntu-latest'
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          slug: o3co/py.hocon
+          files: coverage.xml
+          fail_ci_if_error: false

hocon_parser-1.8.0/.gitignore

@@ -0,0 +1,30 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+
+# Virtualenv
+.venv/
+
+# Tool caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# Conformance corpus (synced from o3co/xx.hocon via `make testdata`)
+tests/conformance/testdata/
+.xx-hocon-version
+
+# Editor / OS
+.DS_Store
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Claude Code (local-only settings)
+.claude/settings.local.json

hocon_parser-1.8.0/CHANGELOG.md

@@ -0,0 +1,80 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [1.8.0] - 2026-07-16
+
+Initial published release. The version is aligned to the sibling o3co
+implementations (go.hocon / rs.hocon / ts.hocon, all at 1.8.0), which move in
+lockstep — py.hocon enters that lockstep at parity rather than starting a
+separate 0.x line. Distributed on PyPI as `hocon-parser` (imported as `hocon`).
+
+### Added
+
+- `tools/hocon_json.py` — differential-harness adapter registering py.hocon in
+  xx.hocon's cross-impl driver (`generate/DifferentialDriver.java`). Parses +
+  resolves a `.conf` and emits canonical JSON to stdout (via the oracle-aligned
+  `_render_json_for_test` renderer, mirroring ts.hocon), or a single-line
+  `{"__error__":{type,message}}` record + exit 3 on failure. `tests/test_hocon_json_adapter.py`
+  runs it over the whole spec-corpus and asserts equality with the
+  Lightbend-generated expected JSON (an in-repo oracle differential), plus
+  CLI-contract and process-env-resolution checks. `ruff` now also lints `tools`.
+- Conformance-corpus expansion — five new fixture harnesses closing the gap to
+  the sibling test surface (full suite: 306 passed / 1 skipped / 4 xfailed):
+  - `tests/conformance/test_error_fixtures.py` — 38 error fixtures
+    (`-expected-error.json` + `.error` sidecars: subst-tokenize st-err,
+    concat-errors, include-reservation, env-var-list, self-ref-lookback sr05,
+    path-expr-whitespace pw06, …) with ts-parity error-class pinning; us15 is
+    a strict-xfail tripwire for the `+`-reservation gap shared by all siblings
+    (ts#73 / rs `#[should_panic]`).
+  - `tests/test_units_default.py` — units-default ud/ub/un accessor fixtures
+    at rs parity. Known cross-impl note: negative durations stay signed
+    (Lightbend/go-faithful; rs rejects only because `std::time::Duration` is
+    unsigned) — pinned both ways (passing signed test + strict-xfail rs
+    tripwire on ud06).
+  - `tests/test_deferred_resolution_fixtures.py` — all 31 E12 scenario-YAML
+    fixtures (dr01–dr30 incl. dr11a/b) via a dependency-free purpose-built
+    scenario loader, plus dr19/dr29 programmatic companions; consumes dr12 and
+    dr17, which the sibling YAML runners skip.
+  - `tests/test_properties_conflict_fixtures.py` — pc01–pc04 (S23.4
+    object-wins, input-order independent).
+  - `tests/test_include_package_fixtures.py` — ipk01–ipk14 E11 scenarios via
+    the `package_resolver` kwarg (ipk03 N/A per E11 decision 3, as in ts).
+- `Config.get_period` + `Period(years, months, days)` frozen dataclass —
+  S20.1–S20.4 period accessor at rs.hocon parity (ts / go remain ➖ here):
+  integer-only per Lightbend `Integer.parseInt` (fractional rejected, up03),
+  bare numbers default to days (HOCON.md L1321), lowercase-only units
+  (`d`/`day`/`days`, `w`/`week`/`weeks` folded into days, `m`/`mo`/`month`/
+  `months`, `y`/`year`/`years`), negative periods permitted, i32-bounded.
+- Initial parser implementation, ported from `@o3co/ts.hocon` with the same
+  3-stage pipeline (Lexer → Parser → Resolver):
+  - **Lexer** — full HOCON whitespace set, quoted / triple-quoted / unquoted
+    strings, `${...}` / `${?...}` substitutions with the `[]` list suffix (S13c),
+    path-expression whitespace tracking (E13).
+  - **Parser** — objects, arrays, value concatenation, path expressions with
+    space-concat (S10.8), `+=` append, `include` (bare / `file(...)` /
+    `package(...)` / `required(...)`), `include` key-path reservation (S12.5).
+  - **Resolver** — two-phase build/resolve, substitution resolution with
+    self-reference lookback and chained-self-append folding (S13a, #118/#120),
+    delayed object merge, env-var and env-var-list fallback (S13c), numeric
+    object → array conversion (S15), `.properties` includes (S23).
+  - **Config accessors** (rs.hocon-style snake_case): `get` / `get_string` /
+    `get_number` / `get_int` / `get_float` / `get_boolean` / `get_duration` /
+    `get_bytes` / `get_config` / `get_list` / `get_value` / `has` / `keys` /
+    `to_object`, plus deferred resolution (`resolve` / `resolve_with` /
+    `with_fallback`, E12) and `from_map` / `empty` value factories.
+  - Duration / byte-size coercion with case-sensitive duration units (S19.8) and
+    power-of-two single-letter byte abbreviations (S21.4).
+- Conformance harness against the shared o3co/xx.hocon corpus: **134/134 spec
+  corpus** and **14/16 Lightbend suite** (the 2 held-out fixtures reference JVM
+  system properties `${?java.version}` / `${?user.home}` — every non-JVM parser
+  caps at 14/16). At parity with go.hocon and rs.hocon.
+- Project scaffold: package layout mirroring the sibling implementations, error
+  type hierarchy (`ParseError`, `ResolveError`, `PackageLookupError`,
+  `ConfigError`, `NotResolvedError`), and tooling (hatchling, pytest, mypy
+  strict, ruff) with the `make testdata` corpus-sync target.

hocon_parser-1.8.0/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing to py.hocon
+
+Thank you for your interest in contributing!
+
+## Reporting Bugs
+
+Please open a [GitHub Issue](https://github.com/o3co/py.hocon/issues) and include:
+
+- Python version (`python --version`)
+- py.hocon version
+- A minimal reproducing HOCON snippet
+- Expected vs. actual behavior
+
+## Proposing Features
+
+Open an issue first to discuss the proposal before sending a PR. This avoids
+wasted effort if the direction doesn't fit the project scope.
+
+## Development Setup
+
+Requires Python 3.11+.
+
+```bash
+git clone https://github.com/o3co/py.hocon.git
+cd py.hocon
+make setup     # creates .venv and installs the package + dev tools (editable)
+make check     # ruff + mypy --strict + pytest
+```
+
+`make setup` uses `python3.11` by default; override with `make setup PYTHON=python3.12`.
+
+## Running Tests
+
+```bash
+# All tests (unit + conformance)
+make test
+
+# Lint / type-check / tests together
+make check
+
+# Sync the shared conformance corpus from o3co/xx.hocon, then run it
+make testdata
+make test
+
+# Micro-benchmarks
+make bench
+```
+
+The conformance suite (`tests/conformance/`) drives every fixture from
+[o3co/xx.hocon](https://github.com/o3co/xx.hocon) through the parser and compares
+the resolved output against Lightbend-generated expected JSON. Run `make testdata`
+once to fetch the corpus (git-ignored); the suite skips gracefully if it is absent.
+
+## Code Style
+
+- `mypy --strict` throughout — no untyped defs, no implicit `Any`
+- `ruff` for lint + import ordering (`make lint`)
+- Keep the public API consistent with ts.hocon / rs.hocon (throwing typed getters,
+  snake_case accessor names)
+- New features must include tests; spec-relevant changes should add or update a
+  conformance fixture in xx.hocon, not just a local test
+- Modules under `hocon._internal` are **not** part of the public API
+- Preserve cross-language parity: this parser mirrors
+  [ts.hocon](https://github.com/o3co/ts.hocon)'s 3-stage pipeline
+  (Lexer → Parser → Resolver). A spec-behavior change here should be reconciled
+  with the sibling implementations.
+
+## Submitting a Pull Request
+
+1. Fork the repository and create a branch from `main`
+2. Write tests for your change
+3. Ensure `make check` passes (ruff + mypy --strict + pytest)
+4. Update `CHANGELOG.md` under `[Unreleased]` for any user-facing change
+5. Open a PR against `main` with a clear description of what and why
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the
+[Apache License 2.0](LICENSE).

hocon_parser-1.8.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 1o1 Co. Ltd.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

hocon_parser-1.8.0/Makefile

@@ -0,0 +1,61 @@
+PYTHON ?= python3.11
+VENV   := .venv
+
+TESTDATA_REPO := o3co/xx.hocon
+TESTDATA_REF  := main
+TESTDATA_DIR  := tests/conformance/testdata
+
+.PHONY: setup test lint typecheck check bench testdata clean
+
+# Bootstrap the dev venv (idempotent).
+setup:
+	test -d $(VENV) || $(PYTHON) -m venv $(VENV)
+	$(VENV)/bin/pip install --quiet --upgrade pip
+	$(VENV)/bin/pip install --quiet -e . --group dev
+
+test:
+	$(VENV)/bin/python -m pytest
+
+lint:
+	$(VENV)/bin/ruff check src tests benchmarks tools
+
+typecheck:
+	$(VENV)/bin/mypy
+
+check: lint typecheck test
+
+bench:
+	$(VENV)/bin/python benchmarks/bench.py
+
+# Sync the conformance corpus (fixtures + Lightbend-generated expected JSON)
+# from o3co/xx.hocon. Skips the download when the pinned sha is current.
+# The sha is resolved via `git ls-remote` (not api.github.com) so CI runners
+# sharing an egress IP don't trip the unauthenticated API rate limit, and the
+# tarball is fetched by that sha so the recorded pin is exactly what landed
+# (same convention as rs.hocon).
+testdata:
+	@set -e; \
+	sha="$$(git ls-remote "https://github.com/$(TESTDATA_REPO).git" "$(TESTDATA_REF)" | head -1 | cut -f1)"; \
+	if [ -z "$$sha" ]; then \
+	  echo "error: could not resolve $(TESTDATA_REPO)@$(TESTDATA_REF) SHA via git ls-remote" >&2; \
+	  exit 1; \
+	fi; \
+	if [ -f .xx-hocon-version ] && [ -d "$(TESTDATA_DIR)/hocon" ] && [ -d "$(TESTDATA_DIR)/expected" ] && \
+	   [ "$$sha" = "$$(cat .xx-hocon-version)" ]; then \
+	  echo "Conformance corpus up to date ($$sha)"; \
+	  exit 0; \
+	fi; \
+	tmpdir="$$(mktemp -d)"; \
+	trap 'rm -rf "$$tmpdir"' EXIT INT TERM; \
+	curl -sfL "https://github.com/$(TESTDATA_REPO)/archive/$$sha.tar.gz" -o "$$tmpdir/archive.tar.gz"; \
+	tar xzf "$$tmpdir/archive.tar.gz" -C "$$tmpdir" --strip-components=1; \
+	rm -rf "$(TESTDATA_DIR)/hocon" "$(TESTDATA_DIR)/expected"; \
+	mkdir -p "$(TESTDATA_DIR)"; \
+	cp -R "$$tmpdir/testdata/hocon" "$(TESTDATA_DIR)/hocon"; \
+	cp -R "$$tmpdir/expected/hocon" "$(TESTDATA_DIR)/expected"; \
+	printf '%s\n' "$$sha" > .xx-hocon-version; \
+	echo "Done. Fetched $$sha"
+
+clean:
+	rm -rf $(VENV) dist build .pytest_cache .mypy_cache .ruff_cache
+	find . -type d -name __pycache__ -exec rm -rf {} +