Open
Conversation
Contributor
|
Thanks for this contribution! Unfortunately, we can't merge this right now because Hatchling doesn't support the older Python versions that djangoql still supports. We'll be able to accept this once we drop support for older Python versions. |
Contributor
Author
|
@ivanbkl Ah, right! Is there a timeline for dropping that support? |
Contributor
|
@akx No concrete timeline right now. |
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.
This PR modernizes the build process for the library to be PEP517 using Hatchling as the build backend.
As visible from the Beyond Compare screenshot below, the built archives (with
uv build, but that shouldn't matter) are effectively the same, modulo of course files that aren't included anymore.