fix: restore rugguard.py release shim#52
Open
leo-guinan wants to merge 1 commit into
Open
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
2 participants
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.
Summary
scripts/rugguard.pyas a legacy launcher/import shim after the package refactorscripts/rugguard.pyto release assets so the documentedreleases/latest/download/rugguard.pypath can work again on the next tagscripts/-first import pattern used by the current test suiteBounty / issue target
rugguard.pyrelease download path)Verification
uv run ruff check scripts/rugguard.pyuv run pytest -q -k "not slow"-> 43 passed, 7 deselecteduv run pytest -q tests/test_checks.py::TestCLI::test_cli_help-> 1 passeduv build-> built sdist and wheel; wheel includesscripts/rugguard.pyNote
A live BONK CLI JSON test timed out against public RPC in 60s during verification; the shim itself was verified with help/import/unit/build paths. Public RPC remains the miserable little bottleneck, as usual.