cobol-parser 3.0.0__tar.gz → 3.1.0__tar.gz

{cobol_parser-3.0.0/cobol_parser.egg-info → cobol_parser-3.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cobol-parser
-Version: 3.0.0
+Version: 3.1.0
 Summary: A comprehensive COBOL parser for Python with IBM Enterprise COBOL focus
 Author-email: Samuel Dion <sam94dion@gmail.com>
 License: AGPL-3.0-or-later
@@ -25,8 +25,11 @@ Provides-Extra: fast
 Requires-Dist: cython>=3.0; extra == "fast"
 Provides-Extra: jcl
 Requires-Dist: jcl-parser>=2.0.0; extra == "jcl"
+Provides-Extra: mcp
+Requires-Dist: mcp<2,>=1.10; extra == "mcp"
 Provides-Extra: dev
 Requires-Dist: jcl-parser>=2.0.0; extra == "dev"
+Requires-Dist: mcp<2,>=1.10; extra == "dev"
 Requires-Dist: pytest>=7.0.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
 Requires-Dist: pytest-xdist>=3.0.0; extra == "dev"
@@ -68,8 +71,20 @@ uv tool install .            # from a clone of this repo
 uv tool install --editable . # dev mode: picks up code changes without reinstalling
 ```
 
-`uv tool install` builds the Cython fast-path extensions as part of the
-install, so the CLI runs at full speed. Verify it worked from anywhere:
+The install is pure Python by default: no C compiler needed. The optional
+Cython accelerators (about 3x lexer throughput) are an opt-in, chosen by one
+environment variable both when building and when running:
+
+```bash
+COBOLPARSER_ACCEL=1 uv tool install . --reinstall   # compile them
+export COBOLPARSER_ACCEL=1                          # and use them
+```
+
+The PyPI wheels already contain the compiled accelerators, so for a
+`pip install cobol-parser` setting `COBOLPARSER_ACCEL=1` at run time is
+enough. Without the variable, a compiled extension is ignored.
+
+Verify it worked from anywhere:
 
 ```bash
 cobol-parser --version

{cobol_parser-3.0.0 → cobol_parser-3.1.0}/README.md

@@ -25,8 +25,20 @@ uv tool install .            # from a clone of this repo
 uv tool install --editable . # dev mode: picks up code changes without reinstalling
 ```
 
-`uv tool install` builds the Cython fast-path extensions as part of the
-install, so the CLI runs at full speed. Verify it worked from anywhere:
+The install is pure Python by default: no C compiler needed. The optional
+Cython accelerators (about 3x lexer throughput) are an opt-in, chosen by one
+environment variable both when building and when running:
+
+```bash
+COBOLPARSER_ACCEL=1 uv tool install . --reinstall   # compile them
+export COBOLPARSER_ACCEL=1                          # and use them
+```
+
+The PyPI wheels already contain the compiled accelerators, so for a
+`pip install cobol-parser` setting `COBOLPARSER_ACCEL=1` at run time is
+enough. Without the variable, a compiled extension is ignored.
+
+Verify it worked from anywhere:
 
 ```bash
 cobol-parser --version

{cobol_parser-3.0.0 → cobol_parser-3.1.0/cobol_parser.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cobol-parser
-Version: 3.0.0
+Version: 3.1.0
 Summary: A comprehensive COBOL parser for Python with IBM Enterprise COBOL focus
 Author-email: Samuel Dion <sam94dion@gmail.com>
 License: AGPL-3.0-or-later
@@ -25,8 +25,11 @@ Provides-Extra: fast
 Requires-Dist: cython>=3.0; extra == "fast"
 Provides-Extra: jcl
 Requires-Dist: jcl-parser>=2.0.0; extra == "jcl"
+Provides-Extra: mcp
+Requires-Dist: mcp<2,>=1.10; extra == "mcp"
 Provides-Extra: dev
 Requires-Dist: jcl-parser>=2.0.0; extra == "dev"
+Requires-Dist: mcp<2,>=1.10; extra == "dev"
 Requires-Dist: pytest>=7.0.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
 Requires-Dist: pytest-xdist>=3.0.0; extra == "dev"
@@ -68,8 +71,20 @@ uv tool install .            # from a clone of this repo
 uv tool install --editable . # dev mode: picks up code changes without reinstalling
 ```
 
-`uv tool install` builds the Cython fast-path extensions as part of the
-install, so the CLI runs at full speed. Verify it worked from anywhere:
+The install is pure Python by default: no C compiler needed. The optional
+Cython accelerators (about 3x lexer throughput) are an opt-in, chosen by one
+environment variable both when building and when running:
+
+```bash
+COBOLPARSER_ACCEL=1 uv tool install . --reinstall   # compile them
+export COBOLPARSER_ACCEL=1                          # and use them
+```
+
+The PyPI wheels already contain the compiled accelerators, so for a
+`pip install cobol-parser` setting `COBOLPARSER_ACCEL=1` at run time is
+enough. Without the variable, a compiled extension is ignored.
+
+Verify it worked from anywhere:
 
 ```bash
 cobol-parser --version

{cobol_parser-3.0.0 → cobol_parser-3.1.0}/cobol_parser.egg-info/SOURCES.txt

@@ -11,6 +11,7 @@ cobol_parser.egg-info/requires.txt
 cobol_parser.egg-info/top_level.txt
 cobolparser/__init__.py
 cobolparser/__main__.py
+cobolparser/_accel.py
 cobolparser/_data_fast.c
 cobolparser/_data_fast.pyx
 cobolparser/_errors.py
@@ -29,10 +30,12 @@ cobolparser/profiling.py
 cobolparser/py.typed
 cobolparser/scan.py
 cobolparser/analysis/__init__.py
+cobolparser/analysis/_cics.py
 cobolparser/analysis/_files.py
 cobolparser/analysis/_names.py
 cobolparser/analysis/_procedures.py
 cobolparser/analysis/_sql_flow.py
+cobolparser/analysis/_sql_whenever.py
 cobolparser/analysis/ast_diff.py
 cobolparser/analysis/boundary_inventory.py
 cobolparser/analysis/business_rules.py
@@ -47,6 +50,7 @@ cobolparser/analysis/domains.py
 cobolparser/analysis/field_lineage.py
 cobolparser/analysis/host_var_resolver.py
 cobolparser/analysis/ims_segment_analyzer.py
+cobolparser/analysis/invocation_counts.py
 cobolparser/analysis/io_coverage_reporter.py
 cobolparser/analysis/io_diagnostics.py
 cobolparser/analysis/io_logger.py
@@ -116,6 +120,12 @@ cobolparser/jcl/__init__.py
 cobolparser/jcl/bindings.py
 cobolparser/jcl/models.py
 cobolparser/jcl/parser.py
+cobolparser/mcp/__init__.py
+cobolparser/mcp/codebase_index.py
+cobolparser/mcp/envelope.py
+cobolparser/mcp/server.py
+cobolparser/mcp/tools.py
+cobolparser/mcp/workspace.py
 cobolparser/models/__init__.py
 cobolparser/models/ast_base.py
 cobolparser/models/data_items.py
@@ -196,4 +206,5 @@ cobolparser/preprocess/path_resolver.py
 cobolparser/preprocess/replace_statement.py
 cobolparser/preprocess/source_format.py
 tests/test_all_samples.py
+tests/test_okf_claims.py
 tests/test_okf_staleness_map.py

{cobol_parser-3.0.0 → cobol_parser-3.1.0}/cobol_parser.egg-info/requires.txt

@@ -1,6 +1,7 @@
 
 [dev]
 jcl-parser>=2.0.0
+mcp<2,>=1.10
 pytest>=7.0.0
 pytest-cov>=4.0.0
 pytest-xdist>=3.0.0
@@ -19,5 +20,8 @@ cython>=3.0
 [jcl]
 jcl-parser>=2.0.0
 
+[mcp]
+mcp<2,>=1.10
+
 [profiling]
 psutil>=5.9

{cobol_parser-3.0.0 → cobol_parser-3.1.0}/cobolparser/__init__.py

@@ -231,7 +231,7 @@ from .scan import (
 CobolParseError = ParseError
 
 # Version info
-__version__ = "3.0.0"  # x-release-please-version
+__version__ = "3.1.0"  # x-release-please-version
 __author__ = "Samuel Dion"
 __license__ = "AGPL-3.0-or-later"
 

cobol_parser-3.1.0/cobolparser/_accel.py

@@ -0,0 +1,27 @@
+"""Opt-in switch for the optional Cython accelerators.
+
+The pure-Python implementation is the default backend. The three compiled
+accelerators (``_lexer_fast``, ``_preprocess_fast``, ``_data_fast``) are used
+only when ``COBOLPARSER_ACCEL=1`` is set in the environment -- at build time,
+so ``setup.py`` compiles them, and at import time, so the modules that own a
+fast path swap it in. An installed extension is ignored without the variable,
+so a stale or mismatched binary can never change what a default install does.
+
+Zero internal dependencies: ``setup.py`` does not import this module (it reads
+the same variable itself), but every runtime import site does.
+"""
+
+import os
+
+ENV_VAR = "COBOLPARSER_ACCEL"
+
+_TRUTHY = frozenset({"1", "true", "yes", "on"})
+
+
+def accelerators_enabled() -> bool:
+    """True when the environment opts in to the Cython accelerators.
+
+    Read on every call rather than cached, so a test can flip the variable and
+    reload a module that owns a fast path.
+    """
+    return os.environ.get(ENV_VAR, "").strip().lower() in _TRUTHY