Add py.typed marker file for PEP-561 support - #848
Closed
coreegor wants to merge 1 commit into
Closed
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
Hi, @coreegor, thank you for your contribution! Turns out it's a little bit trickier than simply adding py.typed because the API is exposed from a separate module, which is outside the allure_commons package. The solution is to convert allure from a module to a package and I've addressed that in #850. TBH, I should've merged your PR first instead of just replacing it with another one. I apologize for that. |
Sorry, something went wrong.
Copy link
Copy Markdown
Author
|
Hi, @delatrie |
Sorry, something went wrong.
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
2 participants
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.
Context
Add py.typed marker file for the PEP-561 support
fixes #731
Checklist