Suggestion: Add Mypy library stubs / typing

[OscarVanL]

I get this error from Mypy:

src/py_utils/headers.py:1: error: Cannot find implementation or library stub for module named "secure"  [import-not-found]
src/py_utils/headers.py:1: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports

It'd be great if the library provided typing for Mypy 😁

[cak]

Thanks for the suggestion, Oscar! That’s an excellent point about Mypy. I’ll look into why Mypy is showing errors and work on a fix for the next release. Appreciate your contribution!

[cak]

Also, @OscarVanL, could you please double-check that secure is installed correctly in your environment? According to the Mypy documentation (https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports), the ‘Cannot find implementation’ error could happen if the package isn’t installed or if the py.typed marker isn’t being detected. Let me know if that helps, and I’ll continue to investigate on my side as well!

[OscarVanL]

Thanks, I did double-check this and the package is installed in the environment I run mypy. I have seen this same error message in the past when packages are untyped (or for whatever reason mypy can't use the typing).

[cak]

Hi @OscarVanL,

Thanks again for raising this.

Typing has been significantly tightened up as part of the v2.0 work, including improvements to public APIs and framework integrations. I’ve published a release candidate (2.0.0rc1) and would really appreciate a quick sanity check to see if it resolves the typing issues you were running into.

You can try it with:

pip install secure==2.0.0rc1
# or
uv pip install secure==2.0.0rc1

If you’re still seeing gaps or regressions, concrete examples (mypy errors, missing types, etc.) would be very helpful before the final release.

Thanks for the early feedback, it helped shape a lot of the v2 cleanup.