Repository navigation
Prepare TrainCheck 0.2.0 and validate release distributions - #152
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This prepares TrainCheck 0.2.0 from the reviewed main commit
205a687after #151. PyPI currently publishes 0.1.2. The accumulated inference, tracing, and validation changes warrant a new minor beta release.The package's four console-entrypoint declarations fail standard
importlib.metadata.EntryPoint.load()in fresh interpreters, although pip-generated wrappers happen to work via import side effects. Change them to directmodule:functiontargets: 4/4 standard loads fail before; 4/4 pass after. A typed installed-release validator checks actual distribution metadata, environment location, and independent command loading.The source archive previously included test files without their fixtures or imported tools. Include those source-only dependencies and the release documentation in the sdist; keep wheel package selection unchanged. Add five negative metadata/location tests, bump the package version, and document reproducible build/publication steps. No training, tracing, or inference algorithm changes are introduced here.
Validation:
twine check --strict.pip check: no broken requirements.--helpoutside the checkout.967070c7e3d421e368de6dde4fd731cab7d9750f.The known three unrelated repository-wide formatting failures remain outside this change. Installed tests use the recorded runtime versions; this does not establish compatibility with every version allowed by the currently unbounded dependency declarations. Benchmarks/fresh-validation utilities remain source-only.
Release notes retain the original measured performance comparisons and their limitations; this packaging change makes no new speedup claim. The new direct inference comparison and tracing hotspot audit are recorded separately.
Evidence and inspected distributions are retained under
outputs/release-20261026/. After this main-targeted PR lands, create a signedv0.2.0tag, publish the GitHub release, and upload the exact inspected artifacts to PyPI using the maintainer's configured project token. PyPI authentication remains pending.