Align setUp and tearDown type signatures with unittest and rdflib.plugin

[ajnelson-nist]

The references below indicate the type requirements' sources.

When reviewing subclasses of GraphTestCase, setUp and tearDown did no further work than the parent class GraphTestCase once the signatures were aligned with typeshed.stdlib, so the methods were removed.

The first patch was driven by the following command after activating type review on setUp and tearDown (adding -> None):

mypy test/test_sqlalchemy_sqlite.py

The first patch was then tested with the following command after identifying sibling ("cousin?") classes of the SQLite test. This command raised no errors after deactivating type review (adding # type: ignore) on a package that does not currently provide type signatures:

mypy \
  test/test_sqlalchemy_mysql.py \
  test/test_sqlalchemy_postgresql.py \
  test/test_sqlalchemy_postgresql_pg8000.py \
  test/test_sqlalchemy_sqlite.py

Note: The first patch was not tested by re-running the test suite. However, I do think it will help with future review.

Disclaimer:

Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose.

References

• https://github.com/RDFLib/rdflib/blob/7.1.1/rdflib/plugin.py#L128
• https://github.com/python/typeshed/blob/b40eb642e00c538e29fb037992eb4b21d9ff108c/stdlib/unittest/case.pyi#L119-L120

[ajnelson-nist]

Force-pushing to fix a typo in the commit message.

[ajnelson-nist]

@nicholascar , @edmondchuc - I came across this open PR. I'm not sure why CI is just listing "Waiting for status to be reported," but it seems to still be waiting after pushing the "Update" GitHub button (triggering a catch-up merge). Is there an approval one of you needs to give?

[edmondchuc]

I can't see anything from my side to trigger the CI. It looks like the other PRs are stuck in the same state too.

Googling suggests there may be some branch protection rule in place that's blocking it. Might need someone with elevated privileges to dig into the settings to check that.