Open
Conversation
Contributor
|
Relates to: #1158 |
(cherry picked from commit 1044a5fd6196d2876ca361eb24d731efe087cf73)
Author
|
With the original change the python files were not included in the build by hatchling, which i just noticed. |
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.
Fixes
The previous setup.py relied on a legacy setuptools environment where pkg_resources was assumed to be available. In modern, slim CI environments using uv, build isolation often lacks this deprecated module, leading to the ModuleNotFoundError. Transitioning to pyproject.toml with hatchling eliminates this legacy dependency and explicitly defines the build requirements, ensuring compatibility with modern Python packaging standards.