test: Fix mypy strict errors in unit tests
The unit test files below test/unit/python/jw/pkg/lib/ define Cmd and App subclasses with unannotated methods: __init__(), add_arguments(), _run() and close() lack signatures, the made class attribute lacks a type, and the _cleanup() and exit_context() helpers are untyped, so a strict mypy run over the test tree fails on them. Likewise, the ExecApp and version tests carry list formatting that yapf rejects. Annotate the test classes following the library conventions: parent is App | Cmd, the parser is ArgumentParser, and args is Namespace, and mark every overridden method with @override. Guard the imports that are only used for annotations behind TYPE_CHECKING, and add the future annotations import so they stay out of the runtime path. Then reformat the test tree with yapf. That folds the opts list of the ExecApp test and re-indents the rejected operator list of the version test. Signed-off-by: Jan Lindemann <jan@janware.com> Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v0.85.1
This commit is contained in:
parent
432b07060b
commit
64f1a73650
4 changed files with 46 additions and 27 deletions
|
|
@ -233,16 +233,16 @@ for bad in ['', 'foo =', ' = 1.0']:
|
|||
# Operators outside the supported set are rejected when parsed,
|
||||
# not folded into the package name or deferred to expansion
|
||||
for bad in [
|
||||
'foo ~= 1.0',
|
||||
'foo~=1.0',
|
||||
'foo ~ 1.0',
|
||||
'foo != 1.0',
|
||||
'foo!=1.0',
|
||||
'foo == 1.0',
|
||||
'foo==1.0',
|
||||
'foo === 1.0',
|
||||
'foo << 1.0',
|
||||
'foo >> 1.0',
|
||||
'foo ~= 1.0',
|
||||
'foo~=1.0',
|
||||
'foo ~ 1.0',
|
||||
'foo != 1.0',
|
||||
'foo!=1.0',
|
||||
'foo == 1.0',
|
||||
'foo==1.0',
|
||||
'foo === 1.0',
|
||||
'foo << 1.0',
|
||||
'foo >> 1.0',
|
||||
]:
|
||||
try:
|
||||
Dependency(bad).full_name
|
||||
|
|
|
|||
Loading…
Reference in a new issue