Skip to content

Potentially wrong location of the py.typed file #267

@s-heppner

Description

@s-heppner

Could it be that the py.typed file should actually be located in the ./pyshacl directory?
We've been having problems with mypy in our CI-pipeline of the PR: eclipse-basyx/basyx-python-sdk#308:

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

I'm no expert on PEP 561 myself, but it seems in this example, the py.typed file is actually located on the same level as the top-level __init__.py.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions