Package does not include the py.typed file?

[AustinScola]

While the repo has a py.typed file and uses annotations, I don't think the py.typed file is being packaged which causes the following error when type checking code which imports piptools:

error: Skipping analyzing "piptools": module is installed, but missing library stubs or py.typed marker  [import]
note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports

I think the solution is to just include package_data = ["py.typed"] in setup.cfg.

As a bonus the classifier Typing :: Typed could also be added.

[FlorentJeannot]

Hello @AustinScola,

FYI, I made a PR to fix this. Just out of curiosity, why do you need to import piptools in your code?

[AustinScola]

Just out of curiosity, why do you need to import piptools in your code?

I have a wrapper script around piptools that adds functionality.

[FlorentJeannot]

Interesting, is this something we could integrate into pip-tools?

[AustinScola]

Maybe? It lets me use a config file to give names to specifications of requirements files and to freeze multiple specifications at once