Update package to use snekpack #171
Merged
Conversation
This file contains 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
|
Hello @cthoyt, we are also actively working on this repository and would appreciate more information on changes that you are proposing to make. Pull requests with no description and no discussion prevent this. |
|
this is just a maintenance PR - no changes in code other than modernizing formatting, packing and CI. I updated the header with a description. |
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.
This PR updates the project structure to follow the standard layout from cookiecutter-snekpack (https://github.com/cthoyt/cookiecutter-snekpack). This can be automatically updated with
cruftas changes in packaging (e.g., with uv) happen over time. Similarly, as we increase code quality standards, this makes it possible to update many repositories at the same time.Making this update was motivated by a recent PR with many code quality issues - it's much easier to give support in these sorts of things by having lots of CI rather than spending person time e.g. on formatting, which is unnecessary given there are automated formatters and checkers.