Make package PEP 561 compliant by including py.typed file

[jonded94]

Description

Using this package in a codebase with mypy unfortunately leads to errors like these:

error: Skipping analyzing "approvaltest.[...]": module is installed, but missing library stubs or py.typed marker  [import-untyped]

This is because this package is not properly PEP 561 compliant.

The solution

Adding a py.typed file since this package already large has type hints, it just wasn't marked as being typed.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

[jonded94]

@isidore any updates on this? This should be a very small, unproblematic change. Let me know what you think.

[JayBazuzi]

This is resolved by #179 .

[jonded94]

Good to know!

Is there any particular reason why this PR was entirely stale for 3 months, just to be replaced by a slightly different PR doing almost the exact same without previous notice?

I'm happy for any positive change here, just wanted to understand the processes a bit better.

[JayBazuzi]

I can't speak for the rest of the crew, but for me - I didn't notice yours until mine was almost done, whoops.

[nitsanavni]

@jonded94 we haven't been paying enough attention to PRs, sorry about that.
To clarify a bit - most development on this project is done in a weekly open ensemble programming session ("open" meaning anyone is welcome) and doesn't get much attention outside those sessions. We tend to focus on a single issue at a time.
We'll be sure to pay more attention to PRs coming from the broader community going forward.
Thanks!