phisql 1.2.0__tar.gz

phisql-1.2.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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 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 Support. 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 support.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Philterd, LLC.
+
+   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.

phisql-1.2.0/MANIFEST.in

@@ -0,0 +1,3 @@
+# Include the spec data copied into the package at build time (see setup.py)
+# so it is present in source distributions as well as wheels.
+recursive-include phisql/_data *.yaml *.json

phisql-1.2.0/PKG-INFO

@@ -0,0 +1,210 @@
+Metadata-Version: 2.4
+Name: phisql
+Version: 1.2.0
+Summary: Python reference parser and compiler for the PhiSQL specification.
+Author-email: "Philterd, LLC" <support@philterd.ai>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/philterd/phisql
+Project-URL: Source, https://github.com/philterd/phisql
+Project-URL: Issues, https://github.com/philterd/phisql/issues
+Project-URL: Documentation, https://philterd.github.io/phisql/
+Keywords: phisql,pii,redaction,deidentification,phileas,privacy
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Compilers
+Classifier: Topic :: Text Processing :: Linguistic
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=5.4
+Requires-Dist: antlr4-python3-runtime==4.13.2
+Provides-Extra: test
+Requires-Dist: pytest>=7.0; extra == "test"
+Requires-Dist: jsonschema>=4.18.0; extra == "test"
+Dynamic: license-file
+
+# PhiSQL Reference Implementation (Python)
+
+The Python reference parser and compiler for the [PhiSQL specification](https://github.com/philterd/phisql/tree/main/spec).
+It is a sibling of the [Java reference implementation](https://github.com/philterd/phisql/tree/main/reference/java) and produces the
+same Phileas JSON output for the same input.
+
+The lexer and parser are generated from
+[`spec/v1.0/grammar/PhiSQL.g4`](https://github.com/philterd/phisql/blob/main/spec/v1.0/grammar/PhiSQL.g4)
+with ANTLR (the same grammar the Java reference generates from). The generated
+sources are committed under [`phisql/_generated/`](phisql/_generated/) so that
+installing and testing this package stays pure-Python, with no Java needed to
+use it. The parser walks its parse tree into the AST the compiler consumes
+(`phisql/parser.py`).
+
+The grammar in the spec remains the single source of truth.
+[`scripts/generate_parser.sh`](scripts/generate_parser.sh) regenerates the
+parser from it, and CI regenerates and runs `git diff --exit-code` over
+`phisql/_generated/`, so any drift between the grammar and the committed parser
+fails the build. (Regenerating needs a JDK to run the ANTLR tool; using and
+testing the package does not.)
+
+The compiler is driven by the catalog YAML files under
+[`spec/v1.0/catalog/`](https://github.com/philterd/phisql/tree/main/spec/v1.0/catalog) — the same files the Java
+reference, the spec validator, and the conformance suite use. There is no copy
+of the catalog or grammar inside this directory; both are read from the spec.
+
+## Requirements
+
+- Python 3.9+
+- [PyYAML](https://pyyaml.org/) (declared as a dependency)
+- [antlr4-python3-runtime](https://pypi.org/project/antlr4-python3-runtime/) (declared as a dependency; loads the generated parser)
+
+A JDK is required only to *regenerate* the parser (see below), not to install,
+use, or test the package.
+
+## Install
+
+```sh
+cd reference/python
+pip install -e ".[test]"
+```
+
+This must be run from a checkout of the repository, because the catalog and
+schema are read from `spec/` and `schema/`. The files are located by walking up
+from the package to find the repository root; set `PHISQL_SPEC_ROOT` to point at
+a checkout's root if you run the package from elsewhere.
+
+## Test
+
+```sh
+cd reference/python
+pytest
+```
+
+The suite mirrors the Java reference's tests:
+
+1. `test_examples_parse.py` parses every `.phisql` file under
+   `../../spec/v1.0/examples/` and asserts it produces no syntax errors.
+2. `test_compiler.py` compiles every redaction example and asserts the output
+   equals the sibling `.json` file (compared as parsed JSON).
+
+These two are the load-bearing assertions that the implementation stays in sync
+with the spec: any grammar change that breaks an example, or any new example
+the parser or compiler can't handle, fails the build.
+
+## Regenerating the parser
+
+The lexer/parser/visitor under `phisql/_generated/` are generated from
+`spec/v1.0/grammar/PhiSQL.g4`. After changing the grammar, regenerate them:
+
+```sh
+cd reference/python
+./scripts/generate_parser.sh
+```
+
+The script downloads the pinned ANTLR tool jar to a gitignored cache on first
+run (override with `ANTLR_JAR=/path/to/antlr-complete.jar`) and needs a JDK on
+`PATH`. Commit the regenerated files. CI runs the same script and fails if the
+committed output differs, so the grammar stays the single source of truth.
+
+## Usage
+
+### Parse
+
+```python
+from phisql import parse
+
+document = parse("POLICY ssn_only; REDACT SSN WITH MASK;")
+# document is an AST (see phisql/ast.py). Walk it directly, or use the compiler.
+```
+
+### Compile to Phileas JSON
+
+```python
+from phisql import Compiler
+
+result = Compiler().compile(
+    "POLICY hipaa_safe_harbor;\n"
+    "DEIDENTIFY SSN AS REDACT, DATE AS TRUNCATE, EMAIL_ADDRESS AS MASK;"
+)
+
+print(result.policy_name())     # "hipaa_safe_harbor"
+print(result.to_json_string())  # Phileas JSON policy
+```
+
+### Compile from a file
+
+```python
+from phisql import Compiler
+
+result = Compiler().compile_file("policies/hipaa-safe-harbor.phisql")
+result.policy_name()  # "hipaa-safe-harbor" (from the filename basename)
+```
+
+The policy name comes from the filename basename. A `POLICY` declaration inside
+the file is optional; when present, its name must match the basename after
+hyphen/underscore normalization (so `hipaa-safe-harbor.phisql` may declare
+`POLICY hipaa_safe_harbor`). The compiler raises a `CompileException` on
+mismatch. This rule is defined in
+[`spec/v1.0/catalog/policy.yaml`](https://github.com/philterd/phisql/blob/main/spec/v1.0/catalog/policy.yaml).
+
+### Command line
+
+```sh
+python -m phisql path/to/policy.phisql      # or: phisql path/to/policy.phisql
+```
+
+It writes the compiled Phileas JSON to stdout. Exit codes form the adapter
+contract the conformance runner relies on: `0` success, `2` parse error, `3`
+compile error, `64` usage error, `1` other I/O error.
+
+### Retrieve the policy schema
+
+An application that depends on `phisql` can read the canonical redaction policy
+JSON Schema straight from the library — no network fetch, no separate checkout —
+exactly as the Java reference exposes it through `ai.philterd.phisql.PolicySchema`:
+
+```python
+from phisql import PolicySchema
+
+PolicySchema.get_supported_schema_version()  # "1.0.0"
+PolicySchema.get_schema()                    # the schema as a JSON string
+PolicySchema.get_schema_dict()               # the schema parsed into a dict
+```
+
+The schema (and the catalog the compiler uses) are copied into the package at
+build time — see [How the spec data is bundled](#how-the-spec-data-is-bundled) —
+so these work from an installed wheel regardless of where it came from.
+
+## How the spec data is bundled
+
+The compiler is driven by the catalog YAML and the policy schema, both of which
+live in the repository root (`spec/` and `schema/`). The build copies them into
+the package at `phisql/_data/` — the Python analogue of the Maven
+`copy-resources` steps that pack the same files into the Java JAR. This is done
+by `setup.py` at build time, so:
+
+- an **installed wheel** (or a Git/path install) is self-contained;
+- a **source checkout** falls back to reading `spec/`/`schema/` directly, so the
+  tests run without a build step;
+- set `PHISQL_SPEC_ROOT` to a repository root to override the lookup explicitly.
+
+The repository remains the single source of truth; `phisql/_data/` is a
+gitignored build artifact, like the Java `target/` resources.
+
+## Scope
+
+Like the Java reference, this compiler targets the redaction subset of PhiSQL
+(REDACT, DEIDENTIFY, IGNORE, DEFINE IDENTIFIER, DEFINE DICTIONARY, DEFINE
+SECTION, DETECT PHEYE, and the CONFIGURE forms) and emits Phileas JSON.
+Discovery statements (FIND PII, DISCOVER ENTITIES, SCAN, SELECT FROM findings)
+parse successfully but are not yet compiled; they target a separate
+discovery-query schema.
+
+## License
+
+Apache License, Version 2.0. See [LICENSE](https://github.com/philterd/phisql/blob/main/LICENSE).

phisql-1.2.0/README.md

@@ -0,0 +1,177 @@
+# PhiSQL Reference Implementation (Python)
+
+The Python reference parser and compiler for the [PhiSQL specification](https://github.com/philterd/phisql/tree/main/spec).
+It is a sibling of the [Java reference implementation](https://github.com/philterd/phisql/tree/main/reference/java) and produces the
+same Phileas JSON output for the same input.
+
+The lexer and parser are generated from
+[`spec/v1.0/grammar/PhiSQL.g4`](https://github.com/philterd/phisql/blob/main/spec/v1.0/grammar/PhiSQL.g4)
+with ANTLR (the same grammar the Java reference generates from). The generated
+sources are committed under [`phisql/_generated/`](phisql/_generated/) so that
+installing and testing this package stays pure-Python, with no Java needed to
+use it. The parser walks its parse tree into the AST the compiler consumes
+(`phisql/parser.py`).
+
+The grammar in the spec remains the single source of truth.
+[`scripts/generate_parser.sh`](scripts/generate_parser.sh) regenerates the
+parser from it, and CI regenerates and runs `git diff --exit-code` over
+`phisql/_generated/`, so any drift between the grammar and the committed parser
+fails the build. (Regenerating needs a JDK to run the ANTLR tool; using and
+testing the package does not.)
+
+The compiler is driven by the catalog YAML files under
+[`spec/v1.0/catalog/`](https://github.com/philterd/phisql/tree/main/spec/v1.0/catalog) — the same files the Java
+reference, the spec validator, and the conformance suite use. There is no copy
+of the catalog or grammar inside this directory; both are read from the spec.
+
+## Requirements
+
+- Python 3.9+
+- [PyYAML](https://pyyaml.org/) (declared as a dependency)
+- [antlr4-python3-runtime](https://pypi.org/project/antlr4-python3-runtime/) (declared as a dependency; loads the generated parser)
+
+A JDK is required only to *regenerate* the parser (see below), not to install,
+use, or test the package.
+
+## Install
+
+```sh
+cd reference/python
+pip install -e ".[test]"
+```
+
+This must be run from a checkout of the repository, because the catalog and
+schema are read from `spec/` and `schema/`. The files are located by walking up
+from the package to find the repository root; set `PHISQL_SPEC_ROOT` to point at
+a checkout's root if you run the package from elsewhere.
+
+## Test
+
+```sh
+cd reference/python
+pytest
+```
+
+The suite mirrors the Java reference's tests:
+
+1. `test_examples_parse.py` parses every `.phisql` file under
+   `../../spec/v1.0/examples/` and asserts it produces no syntax errors.
+2. `test_compiler.py` compiles every redaction example and asserts the output
+   equals the sibling `.json` file (compared as parsed JSON).
+
+These two are the load-bearing assertions that the implementation stays in sync
+with the spec: any grammar change that breaks an example, or any new example
+the parser or compiler can't handle, fails the build.
+
+## Regenerating the parser
+
+The lexer/parser/visitor under `phisql/_generated/` are generated from
+`spec/v1.0/grammar/PhiSQL.g4`. After changing the grammar, regenerate them:
+
+```sh
+cd reference/python
+./scripts/generate_parser.sh
+```
+
+The script downloads the pinned ANTLR tool jar to a gitignored cache on first
+run (override with `ANTLR_JAR=/path/to/antlr-complete.jar`) and needs a JDK on
+`PATH`. Commit the regenerated files. CI runs the same script and fails if the
+committed output differs, so the grammar stays the single source of truth.
+
+## Usage
+
+### Parse
+
+```python
+from phisql import parse
+
+document = parse("POLICY ssn_only; REDACT SSN WITH MASK;")
+# document is an AST (see phisql/ast.py). Walk it directly, or use the compiler.
+```
+
+### Compile to Phileas JSON
+
+```python
+from phisql import Compiler
+
+result = Compiler().compile(
+    "POLICY hipaa_safe_harbor;\n"
+    "DEIDENTIFY SSN AS REDACT, DATE AS TRUNCATE, EMAIL_ADDRESS AS MASK;"
+)
+
+print(result.policy_name())     # "hipaa_safe_harbor"
+print(result.to_json_string())  # Phileas JSON policy
+```
+
+### Compile from a file
+
+```python
+from phisql import Compiler
+
+result = Compiler().compile_file("policies/hipaa-safe-harbor.phisql")
+result.policy_name()  # "hipaa-safe-harbor" (from the filename basename)
+```
+
+The policy name comes from the filename basename. A `POLICY` declaration inside
+the file is optional; when present, its name must match the basename after
+hyphen/underscore normalization (so `hipaa-safe-harbor.phisql` may declare
+`POLICY hipaa_safe_harbor`). The compiler raises a `CompileException` on
+mismatch. This rule is defined in
+[`spec/v1.0/catalog/policy.yaml`](https://github.com/philterd/phisql/blob/main/spec/v1.0/catalog/policy.yaml).
+
+### Command line
+
+```sh
+python -m phisql path/to/policy.phisql      # or: phisql path/to/policy.phisql
+```
+
+It writes the compiled Phileas JSON to stdout. Exit codes form the adapter
+contract the conformance runner relies on: `0` success, `2` parse error, `3`
+compile error, `64` usage error, `1` other I/O error.
+
+### Retrieve the policy schema
+
+An application that depends on `phisql` can read the canonical redaction policy
+JSON Schema straight from the library — no network fetch, no separate checkout —
+exactly as the Java reference exposes it through `ai.philterd.phisql.PolicySchema`:
+
+```python
+from phisql import PolicySchema
+
+PolicySchema.get_supported_schema_version()  # "1.0.0"
+PolicySchema.get_schema()                    # the schema as a JSON string
+PolicySchema.get_schema_dict()               # the schema parsed into a dict
+```
+
+The schema (and the catalog the compiler uses) are copied into the package at
+build time — see [How the spec data is bundled](#how-the-spec-data-is-bundled) —
+so these work from an installed wheel regardless of where it came from.
+
+## How the spec data is bundled
+
+The compiler is driven by the catalog YAML and the policy schema, both of which
+live in the repository root (`spec/` and `schema/`). The build copies them into
+the package at `phisql/_data/` — the Python analogue of the Maven
+`copy-resources` steps that pack the same files into the Java JAR. This is done
+by `setup.py` at build time, so:
+
+- an **installed wheel** (or a Git/path install) is self-contained;
+- a **source checkout** falls back to reading `spec/`/`schema/` directly, so the
+  tests run without a build step;
+- set `PHISQL_SPEC_ROOT` to a repository root to override the lookup explicitly.
+
+The repository remains the single source of truth; `phisql/_data/` is a
+gitignored build artifact, like the Java `target/` resources.
+
+## Scope
+
+Like the Java reference, this compiler targets the redaction subset of PhiSQL
+(REDACT, DEIDENTIFY, IGNORE, DEFINE IDENTIFIER, DEFINE DICTIONARY, DEFINE
+SECTION, DETECT PHEYE, and the CONFIGURE forms) and emits Phileas JSON.
+Discovery statements (FIND PII, DISCOVER ENTITIES, SCAN, SELECT FROM findings)
+parse successfully but are not yet compiled; they target a separate
+discovery-query schema.
+
+## License
+
+Apache License, Version 2.0. See [LICENSE](https://github.com/philterd/phisql/blob/main/LICENSE).

phisql-1.2.0/phisql/__init__.py

@@ -0,0 +1,58 @@
+# Copyright 2026 Philterd, LLC.
+#
+# 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.
+"""
+PhiSQL reference implementation (Python).
+
+The parser is generated from ``spec/v1.0/grammar/PhiSQL.g4`` with ANTLR (see
+``phisql._generated``) and the compiler is driven by the catalog files under
+``spec/v1.0/catalog/``. This package is a sibling of the Java reference
+implementation and produces the same Phileas JSON output.
+
+Quick start::
+
+    from phisql import Compiler
+
+    result = Compiler().compile("POLICY ssn_only; REDACT SSN WITH MASK;")
+    print(result.policy_name())      # "ssn_only"
+    print(result.to_json_string())   # Phileas JSON policy
+"""
+
+from .catalog import Catalog
+from .compiler import Compiler, CompileResult
+from .errors import CompileException, ParseException
+from .phisql import parse
+from .policy_schema import (
+    SUPPORTED_SCHEMA_VERSION,
+    PolicySchema,
+    get_schema,
+    get_schema_dict,
+    get_supported_schema_version,
+)
+
+__version__ = "1.2.0"
+
+__all__ = [
+    "Catalog",
+    "Compiler",
+    "CompileResult",
+    "CompileException",
+    "ParseException",
+    "parse",
+    "PolicySchema",
+    "get_schema",
+    "get_schema_dict",
+    "get_supported_schema_version",
+    "SUPPORTED_SCHEMA_VERSION",
+    "__version__",
+]

phisql-1.2.0/phisql/__main__.py

@@ -0,0 +1,21 @@
+# Copyright 2026 Philterd, LLC.
+#
+# 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.
+"""Enables ``python -m phisql <file.phisql>``."""
+
+import sys
+
+from .cli import main
+
+if __name__ == "__main__":
+    sys.exit(main())