Correct location of py.typed file in MANIFEST.in#267
Merged
lonvia merged 1 commit intoosmcode:masterfrom Sep 27, 2024
Merged
Conversation
Contributor
Is it really?
It only avoids a few warnings: |
Member
Author
|
That is odd. I'm using Debian 12 with backports: So far so good, but when I list the files: |
Contributor
|
The backport doesn't include the file due to the older pybuild in bookworm. The patch does help for the backport: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
py.typedis of course located in the package.@sebastic I noticed that
py.typedis missing in the Debian package for 4.0.0. Could you confirm that this will fix the issue? Then I would do a new release.