Potentially wrong location of the py.typed file
#267
Comments
|
Thanks for this report. The py.typed file was added by another contributor a few years ago, and I assumed it was in the correct location. I'll look into if it needs to be changed. |
s-heppner
added a commit
to rwth-iat/basyx-python-sdk
that referenced
this issue
Nov 6, 2024
Previously, we used version 0.26.0 of pyshacl. This version however had a problem with typing, namely the `py.typed` file was in the wrong location (see [pyshacl#267]). This has been fixed in this new release, therefore we bump the version number in our dependency declaration. This also should fix our CI Pipeline. [pyshacl#267]: RDFLib/pySHACL#267
s-heppner
added a commit
to rwth-iat/basyx-python-sdk
that referenced
this issue
Nov 6, 2024
Previously, we used version 0.26.0 of pyshacl. This version however had a problem with typing, namely the `py.typed` file was in the wrong location (see [pyshacl#267]). This has been fixed in this new release, therefore we bump the version number in our dependency declaration. This also should fix our CI Pipeline. [pyshacl#267]: RDFLib/pySHACL#267
s-heppner
added a commit
to rwth-iat/basyx-python-sdk
that referenced
this issue
Nov 6, 2024
Previously, we used version 0.26.0 of pyshacl. This version however had a problem with typing, namely the `py.typed` file was in the wrong location (see [pyshacl#267]). This has been fixed in this new release, therefore we bump the version number in our dependency declaration. This also should fix our CI Pipeline, as we both fix the mypy issues, as well as some pycodestyle ones. [pyshacl#267]: RDFLib/pySHACL#267
s-heppner
added a commit
to eclipse-basyx/basyx-python-sdk
that referenced
this issue
Nov 12, 2024
Previously, we used version 0.26.0 of pyshacl. This version however had a problem with typing, namely the `py.typed` file was in the wrong location (see [pyshacl#267]). This has been fixed in this new release, therefore we bump the version number in our dependency declaration. This also should fix our CI Pipeline, as we both fix the mypy issues, as well as some pycodestyle ones. [pyshacl#267]: RDFLib/pySHACL#267
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Could it be that the
py.typedfile should actually be located in the./pyshacldirectory?We've been having problems with
mypyin our CI-pipeline of the PR: eclipse-basyx/basyx-python-sdk#308:I'm no expert on PEP 561 myself, but it seems in this example, the
py.typedfile is actually located on the same level as the top-level__init__.py.The text was updated successfully, but these errors were encountered: