echr-py 0.2.0__tar.gz → 0.2.2__tar.gz

{echr_py-0.2.0 → echr_py-0.2.2}/CITATION.cff

@@ -5,7 +5,7 @@ type: software
 authors:
   - family-names: Ridi
     given-names: Niccolo
-version: 0.2.0
+version: 0.2.2
 date-released: 2026-08-21
 license: MIT
 repository-code: "https://github.com/niccoloridi/echr-py"
@@ -29,3 +29,7 @@ references:
       - type: other
         value: "803981"
         description: "European Research Council grant agreement"
+  - type: grant
+    title: "King's Digital Futures Institute Fellowship"
+    authors:
+      - name: "King's College London"

{echr_py-0.2.0/echr_py.egg-info → echr_py-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: echr-py
-Version: 0.2.0
+Version: 0.2.2
 Summary: Pythonic acquisition of HUDOC and HUDOC-EXEC metadata and source documents for ECtHR research.
 Author-email: Niccolo Ridi <niccoloridi@gmail.com>
 License-Expression: MIT
@@ -102,7 +102,7 @@ Dynamic: license-file
   <a href="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml"><img src="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <img src="https://img.shields.io/badge/python-3.11%E2%80%933.14-3776AB.svg" alt="Python 3.11–3.14">
   <a href="https://github.com/niccoloridi/echr-py/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-green.svg" alt="MIT license"></a>
-  <img src="https://img.shields.io/badge/version-0.2.0-blue.svg" alt="Version 0.2.0">
+  <img src="https://img.shields.io/badge/version-0.2.2-blue.svg" alt="Version 0.2.2">
 </p>
 
 `echr-py` is a research engineering toolkit for the case law of the European
@@ -128,12 +128,24 @@ run it hydrated nine documents and wrote 478,151 characters of source-ordered
 text in about 1.1 seconds at concurrency twelve, with the exact query,
 settings, item IDs, hashes, and elapsed time recorded alongside the figure.
 
-![From a HUDOC record to a verified paragraph edge](https://raw.githubusercontent.com/niccoloridi/echr-py/main/docs/images/echr-py-lineage.png)
+One inspectable chain runs from a HUDOC record to a verified paragraph edge.
+Each stage keeps its own identity, so a later stage never overwrites an earlier
+one:
 
-The lineage above is the central idea: retain enough structure and provenance
-to move from a public HUDOC record to a multilingual paragraph, a printed
-citation occurrence, an exact target document, and, when the source supplies a
-pinpoint, a verified target paragraph. [Figure provenance](https://github.com/niccoloridi/echr-py/blob/main/docs/images/echr-py-lineage-provenance.json).
+| Stage | Identity retained at that stage |
+| --- | --- |
+| HUDOC record | item ID, ECLI, language, source checksum |
+| Legal spine | canonical sections, stable block IDs, paragraph addresses, typography |
+| Source identity | majority, individual opinion, footnote, invoking paragraph |
+| Citation occurrence | exact printed span, supporting evidence, pinpoint ownership |
+| Exact target | cited document, cited application, or an explicit unresolved scope |
+| Target paragraph | printed pinpoint mapped to a verified block in the cited document |
+
+That is the central idea: retain enough structure and provenance to move from a
+public HUDOC record to a multilingual paragraph, a printed citation occurrence,
+an exact target document, and, when the source supplies a pinpoint, a verified
+target paragraph. Deterministic identity and graph layers stay separate from
+optional, evidence-verified labels.
 
 ## Start here
 
@@ -483,7 +495,7 @@ without cloning the repository:
 
 ```bash
 claude mcp add --scope user --transport stdio echr-py -- \
-  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.0' echr-py mcp
+  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.2' echr-py mcp
 claude mcp get echr-py
 ```
 
@@ -566,48 +578,33 @@ and graphs without mutating external state. Study jobs require an explicit
 `--enable-jobs` launch configuration with permitted roots, provider and hook
 allowlists, pricing, and per-job budgets.
 
-## Which tool fits which job?
+## See also
 
-The ECtHR research ecosystem now offers several useful but differently scoped
-projects:
+Other projects working on ECtHR material:
 
-| If you need… | Start with… |
-| --- | --- |
-| A multilingual corpus builder with paragraph-, opinion-, footnote-, and exact-citation provenance | **`echr-py`** |
-| A hosted search and reading interface over an existing English snapshot | [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704) |
-| A PyPI extractor and SCL network workflow | [`echr-extractor`](https://pypi.org/project/echr-extractor/) |
-| A ready processed corpus and hosted API | [ECHR Open Data](https://echr-opendata.eu/) |
-| Selective human labels for judicial consideration and Convention provisions | [Mumford et al.](https://doi.org/10.3233/FAIA251584) |
-| A prior-case-retrieval dataset | [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR) |
-
-At the citation layer, `echr-py` combines exact printed occurrences,
-uniquely corroborated procedural-document identity, citation-owned pinpoints, verified
-target paragraphs, majority/opinion/footnote provenance, and portable graph
-exports in one documented contract.
-
-Mumford's annotations are useful for studying selected citation treatments;
-they are not an exhaustive citation inventory or a target-paragraph graph. The
-annotation frame deliberately omits submissions, general-principles material,
-facts, procedure, operative text, appendices, individual opinions, and
-footnotes. A full `echr-py` run can therefore return citation occurrences from
-sections and components outside that annotation frame.
-
-In the frozen 115-document comparison, `echr-py` aligned 5,319 of 5,425
-selected ECHR annotations one-to-one (98.0%): 5,316 by strict source-span
-overlap and three by uniquely normalized context, with 86 ambiguous and 20
-unmatched annotations. These figures measure recovery of the selected
+- [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704)
+- [`echr-extractor`](https://pypi.org/project/echr-extractor/)
+- [ECHR Open Data](https://echr-opendata.eu/)
+- [Mumford et al.](https://doi.org/10.3233/FAIA251584)
+- [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR)
+
+## Benchmark
+
+`echr-py` is compared against the curated Mumford annotation set. Those
+annotations are useful for studying selected citation treatments; they are not
+an exhaustive citation inventory or a target-paragraph graph. The annotation
+frame deliberately omits submissions, general-principles material, facts,
+procedure, operative text, appendices, individual opinions, and footnotes, so a
+full `echr-py` run can return citation occurrences from sections and components
+outside that frame. Any recovery figure measures recovery of those selected
 annotations, not detector precision or completeness over the judgments.
-Exact-document resolution covered 4,629 of the 5,319 aligned references;
-printed application-number identification covered 2,412 of 2,615 references
-that supplied a number, with no conflict among the identifications;
-complete target-paragraph mapping covered 3,794 of 4,543 aligned references
-that carried local pinpoints. Because the reference does not supply canonical
-target item IDs or target-paragraph links, these are coverage measures rather
-than independently verified document- or paragraph-resolution accuracy. The
-importer and methodological comparison remain available for researchers who
-need them, but benchmark mechanics belong in the
-[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md), not on the project
-homepage.
+
+The importer and the methodological comparison remain available for researchers
+who need them, and the measured figures, denominators, hashes and reproduction
+records are kept in the
+[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md)
+and the frozen [benchmark manifest](https://github.com/niccoloridi/echr-py/blob/main/docs/benchmarks/mumford-full-inclusive-audit.json),
+where they can carry their conditions, rather than on the project homepage.
 
 The evidence and dates behind external comparisons are maintained in the
 [claim audit](https://github.com/niccoloridi/echr-py/blob/main/docs/claim-audit.md).
@@ -678,6 +675,8 @@ This research forms part of the Human Rights Nudge project that has received
 funding from the European Research Council (ERC) under the European Union’s
 Horizon 2020 research and innovation programme (Grant agreement No. 803981).
 
+This work was also supported by a King’s Digital Futures Institute Fellowship.
+
 ## Data responsibility
 
 HUDOC and HUDOC-EXEC are evolving public systems. Preserve item IDs, ECLIs,

{echr_py-0.2.0 → echr_py-0.2.2}/README.md

@@ -14,7 +14,7 @@
   <a href="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml"><img src="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <img src="https://img.shields.io/badge/python-3.11%E2%80%933.14-3776AB.svg" alt="Python 3.11–3.14">
   <a href="https://github.com/niccoloridi/echr-py/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-green.svg" alt="MIT license"></a>
-  <img src="https://img.shields.io/badge/version-0.2.0-blue.svg" alt="Version 0.2.0">
+  <img src="https://img.shields.io/badge/version-0.2.2-blue.svg" alt="Version 0.2.2">
 </p>
 
 `echr-py` is a research engineering toolkit for the case law of the European
@@ -40,12 +40,24 @@ run it hydrated nine documents and wrote 478,151 characters of source-ordered
 text in about 1.1 seconds at concurrency twelve, with the exact query,
 settings, item IDs, hashes, and elapsed time recorded alongside the figure.
 
-![From a HUDOC record to a verified paragraph edge](https://raw.githubusercontent.com/niccoloridi/echr-py/main/docs/images/echr-py-lineage.png)
+One inspectable chain runs from a HUDOC record to a verified paragraph edge.
+Each stage keeps its own identity, so a later stage never overwrites an earlier
+one:
 
-The lineage above is the central idea: retain enough structure and provenance
-to move from a public HUDOC record to a multilingual paragraph, a printed
-citation occurrence, an exact target document, and, when the source supplies a
-pinpoint, a verified target paragraph. [Figure provenance](https://github.com/niccoloridi/echr-py/blob/main/docs/images/echr-py-lineage-provenance.json).
+| Stage | Identity retained at that stage |
+| --- | --- |
+| HUDOC record | item ID, ECLI, language, source checksum |
+| Legal spine | canonical sections, stable block IDs, paragraph addresses, typography |
+| Source identity | majority, individual opinion, footnote, invoking paragraph |
+| Citation occurrence | exact printed span, supporting evidence, pinpoint ownership |
+| Exact target | cited document, cited application, or an explicit unresolved scope |
+| Target paragraph | printed pinpoint mapped to a verified block in the cited document |
+
+That is the central idea: retain enough structure and provenance to move from a
+public HUDOC record to a multilingual paragraph, a printed citation occurrence,
+an exact target document, and, when the source supplies a pinpoint, a verified
+target paragraph. Deterministic identity and graph layers stay separate from
+optional, evidence-verified labels.
 
 ## Start here
 
@@ -395,7 +407,7 @@ without cloning the repository:
 
 ```bash
 claude mcp add --scope user --transport stdio echr-py -- \
-  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.0' echr-py mcp
+  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.2' echr-py mcp
 claude mcp get echr-py
 ```
 
@@ -478,48 +490,33 @@ and graphs without mutating external state. Study jobs require an explicit
 `--enable-jobs` launch configuration with permitted roots, provider and hook
 allowlists, pricing, and per-job budgets.
 
-## Which tool fits which job?
+## See also
 
-The ECtHR research ecosystem now offers several useful but differently scoped
-projects:
+Other projects working on ECtHR material:
 
-| If you need… | Start with… |
-| --- | --- |
-| A multilingual corpus builder with paragraph-, opinion-, footnote-, and exact-citation provenance | **`echr-py`** |
-| A hosted search and reading interface over an existing English snapshot | [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704) |
-| A PyPI extractor and SCL network workflow | [`echr-extractor`](https://pypi.org/project/echr-extractor/) |
-| A ready processed corpus and hosted API | [ECHR Open Data](https://echr-opendata.eu/) |
-| Selective human labels for judicial consideration and Convention provisions | [Mumford et al.](https://doi.org/10.3233/FAIA251584) |
-| A prior-case-retrieval dataset | [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR) |
-
-At the citation layer, `echr-py` combines exact printed occurrences,
-uniquely corroborated procedural-document identity, citation-owned pinpoints, verified
-target paragraphs, majority/opinion/footnote provenance, and portable graph
-exports in one documented contract.
-
-Mumford's annotations are useful for studying selected citation treatments;
-they are not an exhaustive citation inventory or a target-paragraph graph. The
-annotation frame deliberately omits submissions, general-principles material,
-facts, procedure, operative text, appendices, individual opinions, and
-footnotes. A full `echr-py` run can therefore return citation occurrences from
-sections and components outside that annotation frame.
-
-In the frozen 115-document comparison, `echr-py` aligned 5,319 of 5,425
-selected ECHR annotations one-to-one (98.0%): 5,316 by strict source-span
-overlap and three by uniquely normalized context, with 86 ambiguous and 20
-unmatched annotations. These figures measure recovery of the selected
+- [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704)
+- [`echr-extractor`](https://pypi.org/project/echr-extractor/)
+- [ECHR Open Data](https://echr-opendata.eu/)
+- [Mumford et al.](https://doi.org/10.3233/FAIA251584)
+- [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR)
+
+## Benchmark
+
+`echr-py` is compared against the curated Mumford annotation set. Those
+annotations are useful for studying selected citation treatments; they are not
+an exhaustive citation inventory or a target-paragraph graph. The annotation
+frame deliberately omits submissions, general-principles material, facts,
+procedure, operative text, appendices, individual opinions, and footnotes, so a
+full `echr-py` run can return citation occurrences from sections and components
+outside that frame. Any recovery figure measures recovery of those selected
 annotations, not detector precision or completeness over the judgments.
-Exact-document resolution covered 4,629 of the 5,319 aligned references;
-printed application-number identification covered 2,412 of 2,615 references
-that supplied a number, with no conflict among the identifications;
-complete target-paragraph mapping covered 3,794 of 4,543 aligned references
-that carried local pinpoints. Because the reference does not supply canonical
-target item IDs or target-paragraph links, these are coverage measures rather
-than independently verified document- or paragraph-resolution accuracy. The
-importer and methodological comparison remain available for researchers who
-need them, but benchmark mechanics belong in the
-[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md), not on the project
-homepage.
+
+The importer and the methodological comparison remain available for researchers
+who need them, and the measured figures, denominators, hashes and reproduction
+records are kept in the
+[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md)
+and the frozen [benchmark manifest](https://github.com/niccoloridi/echr-py/blob/main/docs/benchmarks/mumford-full-inclusive-audit.json),
+where they can carry their conditions, rather than on the project homepage.
 
 The evidence and dates behind external comparisons are maintained in the
 [claim audit](https://github.com/niccoloridi/echr-py/blob/main/docs/claim-audit.md).
@@ -590,6 +587,8 @@ This research forms part of the Human Rights Nudge project that has received
 funding from the European Research Council (ERC) under the European Union’s
 Horizon 2020 research and innovation programme (Grant agreement No. 803981).
 
+This work was also supported by a King’s Digital Futures Institute Fellowship.
+
 ## Data responsibility
 
 HUDOC and HUDOC-EXEC are evolving public systems. Preserve item IDs, ECLIs,

{echr_py-0.2.0 → echr_py-0.2.2/echr_py.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: echr-py
-Version: 0.2.0
+Version: 0.2.2
 Summary: Pythonic acquisition of HUDOC and HUDOC-EXEC metadata and source documents for ECtHR research.
 Author-email: Niccolo Ridi <niccoloridi@gmail.com>
 License-Expression: MIT
@@ -102,7 +102,7 @@ Dynamic: license-file
   <a href="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml"><img src="https://github.com/niccoloridi/echr-py/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <img src="https://img.shields.io/badge/python-3.11%E2%80%933.14-3776AB.svg" alt="Python 3.11–3.14">
   <a href="https://github.com/niccoloridi/echr-py/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-green.svg" alt="MIT license"></a>
-  <img src="https://img.shields.io/badge/version-0.2.0-blue.svg" alt="Version 0.2.0">
+  <img src="https://img.shields.io/badge/version-0.2.2-blue.svg" alt="Version 0.2.2">
 </p>
 
 `echr-py` is a research engineering toolkit for the case law of the European
@@ -128,12 +128,24 @@ run it hydrated nine documents and wrote 478,151 characters of source-ordered
 text in about 1.1 seconds at concurrency twelve, with the exact query,
 settings, item IDs, hashes, and elapsed time recorded alongside the figure.
 
-![From a HUDOC record to a verified paragraph edge](https://raw.githubusercontent.com/niccoloridi/echr-py/main/docs/images/echr-py-lineage.png)
+One inspectable chain runs from a HUDOC record to a verified paragraph edge.
+Each stage keeps its own identity, so a later stage never overwrites an earlier
+one:
 
-The lineage above is the central idea: retain enough structure and provenance
-to move from a public HUDOC record to a multilingual paragraph, a printed
-citation occurrence, an exact target document, and, when the source supplies a
-pinpoint, a verified target paragraph. [Figure provenance](https://github.com/niccoloridi/echr-py/blob/main/docs/images/echr-py-lineage-provenance.json).
+| Stage | Identity retained at that stage |
+| --- | --- |
+| HUDOC record | item ID, ECLI, language, source checksum |
+| Legal spine | canonical sections, stable block IDs, paragraph addresses, typography |
+| Source identity | majority, individual opinion, footnote, invoking paragraph |
+| Citation occurrence | exact printed span, supporting evidence, pinpoint ownership |
+| Exact target | cited document, cited application, or an explicit unresolved scope |
+| Target paragraph | printed pinpoint mapped to a verified block in the cited document |
+
+That is the central idea: retain enough structure and provenance to move from a
+public HUDOC record to a multilingual paragraph, a printed citation occurrence,
+an exact target document, and, when the source supplies a pinpoint, a verified
+target paragraph. Deterministic identity and graph layers stay separate from
+optional, evidence-verified labels.
 
 ## Start here
 
@@ -483,7 +495,7 @@ without cloning the repository:
 
 ```bash
 claude mcp add --scope user --transport stdio echr-py -- \
-  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.0' echr-py mcp
+  "$(command -v uvx)" --from 'echr-py[mcp]==0.2.2' echr-py mcp
 claude mcp get echr-py
 ```
 
@@ -566,48 +578,33 @@ and graphs without mutating external state. Study jobs require an explicit
 `--enable-jobs` launch configuration with permitted roots, provider and hook
 allowlists, pricing, and per-job budgets.
 
-## Which tool fits which job?
+## See also
 
-The ECtHR research ecosystem now offers several useful but differently scoped
-projects:
+Other projects working on ECtHR material:
 
-| If you need… | Start with… |
-| --- | --- |
-| A multilingual corpus builder with paragraph-, opinion-, footnote-, and exact-citation provenance | **`echr-py`** |
-| A hosted search and reading interface over an existing English snapshot | [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704) |
-| A PyPI extractor and SCL network workflow | [`echr-extractor`](https://pypi.org/project/echr-extractor/) |
-| A ready processed corpus and hosted API | [ECHR Open Data](https://echr-opendata.eu/) |
-| Selective human labels for judicial consideration and Convention provisions | [Mumford et al.](https://doi.org/10.3233/FAIA251584) |
-| A prior-case-retrieval dataset | [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR) |
-
-At the citation layer, `echr-py` combines exact printed occurrences,
-uniquely corroborated procedural-document identity, citation-owned pinpoints, verified
-target paragraphs, majority/opinion/footnote provenance, and portable graph
-exports in one documented contract.
-
-Mumford's annotations are useful for studying selected citation treatments;
-they are not an exhaustive citation inventory or a target-paragraph graph. The
-annotation frame deliberately omits submissions, general-principles material,
-facts, procedure, operative text, appendices, individual opinions, and
-footnotes. A full `echr-py` run can therefore return citation occurrences from
-sections and components outside that annotation frame.
-
-In the frozen 115-document comparison, `echr-py` aligned 5,319 of 5,425
-selected ECHR annotations one-to-one (98.0%): 5,316 by strict source-span
-overlap and three by uniquely normalized context, with 86 ambiguous and 20
-unmatched annotations. These figures measure recovery of the selected
+- [HUDOC Researcher](https://doi.org/10.5281/zenodo.21319704)
+- [`echr-extractor`](https://pypi.org/project/echr-extractor/)
+- [ECHR Open Data](https://echr-opendata.eu/)
+- [Mumford et al.](https://doi.org/10.3233/FAIA251584)
+- [ECtHR-PCR](https://github.com/TUMLegalTech/ECHR-PCR)
+
+## Benchmark
+
+`echr-py` is compared against the curated Mumford annotation set. Those
+annotations are useful for studying selected citation treatments; they are not
+an exhaustive citation inventory or a target-paragraph graph. The annotation
+frame deliberately omits submissions, general-principles material, facts,
+procedure, operative text, appendices, individual opinions, and footnotes, so a
+full `echr-py` run can return citation occurrences from sections and components
+outside that frame. Any recovery figure measures recovery of those selected
 annotations, not detector precision or completeness over the judgments.
-Exact-document resolution covered 4,629 of the 5,319 aligned references;
-printed application-number identification covered 2,412 of 2,615 references
-that supplied a number, with no conflict among the identifications;
-complete target-paragraph mapping covered 3,794 of 4,543 aligned references
-that carried local pinpoints. Because the reference does not supply canonical
-target item IDs or target-paragraph links, these are coverage measures rather
-than independently verified document- or paragraph-resolution accuracy. The
-importer and methodological comparison remain available for researchers who
-need them, but benchmark mechanics belong in the
-[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md), not on the project
-homepage.
+
+The importer and the methodological comparison remain available for researchers
+who need them, and the measured figures, denominators, hashes and reproduction
+records are kept in the
+[methodology audit](https://github.com/niccoloridi/echr-py/blob/main/docs/mumford-methodology-audit.md)
+and the frozen [benchmark manifest](https://github.com/niccoloridi/echr-py/blob/main/docs/benchmarks/mumford-full-inclusive-audit.json),
+where they can carry their conditions, rather than on the project homepage.
 
 The evidence and dates behind external comparisons are maintained in the
 [claim audit](https://github.com/niccoloridi/echr-py/blob/main/docs/claim-audit.md).
@@ -678,6 +675,8 @@ This research forms part of the Human Rights Nudge project that has received
 funding from the European Research Council (ERC) under the European Union’s
 Horizon 2020 research and innovation programme (Grant agreement No. 803981).
 
+This work was also supported by a King’s Digital Futures Institute Fellowship.
+
 ## Data responsibility
 
 HUDOC and HUDOC-EXEC are evolving public systems. Preserve item IDs, ECLIs,

{echr_py-0.2.0 → echr_py-0.2.2}/hudoc_py/__init__.py

@@ -37,7 +37,7 @@ from ._sync import (
 from .main.dsl import Q
 from .models import Case, CaseCollection, Document, Sections
 
-__version__ = "0.2.0"
+__version__ = "0.2.2"
 
 __all__ = [
     "__version__",

{echr_py-0.2.0 → echr_py-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "echr-py"
-version = "0.2.0"
+version = "0.2.2"
 description = "Pythonic acquisition of HUDOC and HUDOC-EXEC metadata and source documents for ECtHR research."
 readme = "README.md"
 requires-python = ">=3.11"