pytecode 0.0.1__tar.gz → 0.0.2__tar.gz

{pytecode-0.0.1/pytecode.egg-info → pytecode-0.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytecode
-Version: 0.0.1
+Version: 0.0.2
 Summary: Python library for parsing, manipulating, and emitting JVM class files
 Author: Trenton Smith
 License-Expression: MIT
@@ -166,13 +166,13 @@ uv run ruff check .
 uv run ruff format --check .
 uv run basedpyright
 uv run pytest -q
-uv run python tools\generate_api_docs.py --check
+uv run python tools/generate_api_docs.py --check
 ```
 
 Generate local API reference HTML with:
 
 ```powershell
-uv run python tools\generate_api_docs.py
+uv run python tools/generate_api_docs.py
 ```
 
 Build source and wheel distributions locally:
@@ -181,11 +181,21 @@ Build source and wheel distributions locally:
 uv build
 ```
 
-The `oracle`-marked CFG tests lazily cache ASM 9.7.1 test jars under `.pytest_cache\pytecode-oracle` and also honor manually seeded jars in `tests\resources\oracle\lib`. If `java`, `javac`, or the ASM jars are unavailable, that suite skips without failing the rest of the test run.
+Profile isolated JAR-processing stages without `run.py`'s output overhead:
+
+```powershell
+uv run python tools/profile_jar_pipeline.py path/to/jar.jar
+uv run python tools/profile_jar_pipeline.py path/to/jar.jar --stages class-parse model-lift model-lower
+uv run python tools/profile_jar_pipeline.py path/to/dir/with/jars --stages model-lift model-lower --summary-json output/profiles/common-libs/summary.json
+```
+
+When making runtime-performance changes, prefer checking both a focused jar such as `225.jar` and the wider common-jar corpus so regressions and wins are not judged from a single artifact. A single jar defaults to all stages; directories and multi-jar runs default to `model-lift` and `model-lower`.
+
+The `oracle`-marked CFG tests lazily cache ASM 9.7.1 test jars under `.pytest_cache/pytecode-oracle` and also honor manually seeded jars in `tests/resources/oracle/lib`. If `java`, `javac`, or the ASM jars are unavailable, that suite skips without failing the rest of the test run.
 
 ## Release automation
 
-PyPI releases are published from GitHub Actions by pushing an immutable `v<version>` tag that matches `project.version` in `pyproject.toml`. The release workflow reruns validation on the tagged commit, builds both `sdist` and `wheel` with `uv build`, and publishes from the protected `pypi` environment via PyPI Trusted Publishing.
+PyPI releases are published from GitHub Actions by pushing an immutable `v<version>` tag that matches `project.version` in `pyproject.toml`. The same workflow can also be started manually for an existing tag by supplying a `tag` input. In both cases, the workflow checks out the tagged commit, reruns validation, builds both `sdist` and `wheel` with `uv build`, publishes from the protected `pypi` environment via PyPI Trusted Publishing, and then creates or updates a GitHub Release for the same tag with the built distributions attached.
 
 Release procedure:
 
@@ -195,7 +205,7 @@ uv run ruff check .
 uv run ruff format --check .
 uv run basedpyright
 uv run pytest -q
-uv run python tools\generate_api_docs.py --check
+uv run python tools/generate_api_docs.py --check
 
 git commit -am "Bump version to X.Y.Z"
 git push origin master
@@ -203,16 +213,16 @@ git tag vX.Y.Z
 git push origin vX.Y.Z
 ```
 
-The release workflow rejects tags that do not match `project.version`. Treat release tags as immutable: if a tag or published artifact is wrong, bump to a new version and publish a new tag instead of force-pushing the old one. If the workflow fails before the publish step because of environment approval or a transient PyPI issue, rerun the workflow for the same tag instead of moving the tag.
+The release workflow rejects tags that do not match `project.version`. Treat release tags as immutable: if a tag or published artifact is wrong, bump to a new version and publish a new tag instead of force-pushing the old one. For an existing tag, you can rerun the workflow directly or start it manually from Actions by providing the tag name. The workflow is safe to rerun for the same tag: PyPI uploads skip files that already exist, and the GitHub Release step updates the existing release assets in place if the release was already created.
 
 ## Repository utilities
 
-`run.py` is a manual smoke-test helper that parses a JAR file, writes pretty-printed parsed class structures under `<jar parent>\output\<jar stem>\parsed\`, and writes class-model-derived rewritten `.class` files plus copied resources under `<jar parent>\output\<jar stem>\rewritten\`.
+`run.py` is a manual smoke-test helper that parses a JAR file, writes pretty-printed parsed class structures under `<jar parent>/output/<jar stem>/parsed/`, and writes class-model-derived rewritten `.class` files plus copied resources under `<jar parent>/output/<jar stem>/rewritten/`.
 
 Example:
 
 ```powershell
-uv run python .\run.py .\path\to\input.jar
+uv run python ./run.py ./path/to/input.jar
 ```
 
 The script prints read, parse, lift, write, and rewrite timings plus class and resource counts to stdout.

{pytecode-0.0.1 → pytecode-0.0.2}/README.md

@@ -140,13 +140,13 @@ uv run ruff check .
 uv run ruff format --check .
 uv run basedpyright
 uv run pytest -q
-uv run python tools\generate_api_docs.py --check
+uv run python tools/generate_api_docs.py --check
 ```
 
 Generate local API reference HTML with:
 
 ```powershell
-uv run python tools\generate_api_docs.py
+uv run python tools/generate_api_docs.py
 ```
 
 Build source and wheel distributions locally:
@@ -155,11 +155,21 @@ Build source and wheel distributions locally:
 uv build
 ```
 
-The `oracle`-marked CFG tests lazily cache ASM 9.7.1 test jars under `.pytest_cache\pytecode-oracle` and also honor manually seeded jars in `tests\resources\oracle\lib`. If `java`, `javac`, or the ASM jars are unavailable, that suite skips without failing the rest of the test run.
+Profile isolated JAR-processing stages without `run.py`'s output overhead:
+
+```powershell
+uv run python tools/profile_jar_pipeline.py path/to/jar.jar
+uv run python tools/profile_jar_pipeline.py path/to/jar.jar --stages class-parse model-lift model-lower
+uv run python tools/profile_jar_pipeline.py path/to/dir/with/jars --stages model-lift model-lower --summary-json output/profiles/common-libs/summary.json
+```
+
+When making runtime-performance changes, prefer checking both a focused jar such as `225.jar` and the wider common-jar corpus so regressions and wins are not judged from a single artifact. A single jar defaults to all stages; directories and multi-jar runs default to `model-lift` and `model-lower`.
+
+The `oracle`-marked CFG tests lazily cache ASM 9.7.1 test jars under `.pytest_cache/pytecode-oracle` and also honor manually seeded jars in `tests/resources/oracle/lib`. If `java`, `javac`, or the ASM jars are unavailable, that suite skips without failing the rest of the test run.
 
 ## Release automation
 
-PyPI releases are published from GitHub Actions by pushing an immutable `v<version>` tag that matches `project.version` in `pyproject.toml`. The release workflow reruns validation on the tagged commit, builds both `sdist` and `wheel` with `uv build`, and publishes from the protected `pypi` environment via PyPI Trusted Publishing.
+PyPI releases are published from GitHub Actions by pushing an immutable `v<version>` tag that matches `project.version` in `pyproject.toml`. The same workflow can also be started manually for an existing tag by supplying a `tag` input. In both cases, the workflow checks out the tagged commit, reruns validation, builds both `sdist` and `wheel` with `uv build`, publishes from the protected `pypi` environment via PyPI Trusted Publishing, and then creates or updates a GitHub Release for the same tag with the built distributions attached.
 
 Release procedure:
 
@@ -169,7 +179,7 @@ uv run ruff check .
 uv run ruff format --check .
 uv run basedpyright
 uv run pytest -q
-uv run python tools\generate_api_docs.py --check
+uv run python tools/generate_api_docs.py --check
 
 git commit -am "Bump version to X.Y.Z"
 git push origin master
@@ -177,16 +187,16 @@ git tag vX.Y.Z
 git push origin vX.Y.Z
 ```
 
-The release workflow rejects tags that do not match `project.version`. Treat release tags as immutable: if a tag or published artifact is wrong, bump to a new version and publish a new tag instead of force-pushing the old one. If the workflow fails before the publish step because of environment approval or a transient PyPI issue, rerun the workflow for the same tag instead of moving the tag.
+The release workflow rejects tags that do not match `project.version`. Treat release tags as immutable: if a tag or published artifact is wrong, bump to a new version and publish a new tag instead of force-pushing the old one. For an existing tag, you can rerun the workflow directly or start it manually from Actions by providing the tag name. The workflow is safe to rerun for the same tag: PyPI uploads skip files that already exist, and the GitHub Release step updates the existing release assets in place if the release was already created.
 
 ## Repository utilities
 
-`run.py` is a manual smoke-test helper that parses a JAR file, writes pretty-printed parsed class structures under `<jar parent>\output\<jar stem>\parsed\`, and writes class-model-derived rewritten `.class` files plus copied resources under `<jar parent>\output\<jar stem>\rewritten\`.
+`run.py` is a manual smoke-test helper that parses a JAR file, writes pretty-printed parsed class structures under `<jar parent>/output/<jar stem>/parsed/`, and writes class-model-derived rewritten `.class` files plus copied resources under `<jar parent>/output/<jar stem>/rewritten/`.
 
 Example:
 
 ```powershell
-uv run python .\run.py .\path\to\input.jar
+uv run python ./run.py ./path/to/input.jar
 ```
 
 The script prints read, parse, lift, write, and rewrite timings plus class and resource counts to stdout.

{pytecode-0.0.1 → pytecode-0.0.2}/pyproject.toml

@@ -13,7 +13,7 @@ pytecode = ["py.typed"]
 
 [project]
 name = "pytecode"
-version = "0.0.1"
+version = "0.0.2"
 description = "Python library for parsing, manipulating, and emitting JVM class files"
 readme = "README.md"
 authors = [{ name = "Trenton Smith" }]