typed.py file not included in package (so mypy thinks there is no type info available)

Describe the bug

When I run mypy against my project that uses the msgraph_core library, I get an error indicating that the library has no type information:

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

I see that there is a file called py.typed.txt in the repo (why not just py.typed?) but it doesn't appear in the package that I get via pip (i.e., the one I'd download from https://pypi.org/project/msgraph-core/#files).

Expected behavior

The py.typed file is in the package; mypy (or other type checking tools) have a correct set of types for the package.

How to reproduce

I'm not sure of an exactly minimal repro case, but unless there is something specifically odd with my environment that's contributing, I would guess:

• create a new Python file that imports something from the msgraph_core package
• pip install msgraph-core
• Run mypy against the file

SDK Version

At least 1.3.3, 1.2.1, and 1.1.6

Latest version known to work for scenario above?

I didn't see the py.typed file in 1.1.0, so it must be at least that old

Known Workarounds

Disable type checking for the msgraph-core package.

Debug output

No response

Configuration

• macOS Sequoia , ARM
• I don't think it's specific to this configuration

Other information

No response

Commencez par comparer le fichier py.typed.txt du dépôt avec les fichiers inclus dans le paquet pip sur PyPI, puis examinez les métadonnées du paquet et la configuration de build qui contrôlent l’inclusion. Reproduisez l’erreur d’importation de mypy avec une version installée de msgraph-core et considérez le problème comme terminé lorsque le paquet publié contient le marqueur correct et que mypy reconnaît ses informations de typage.