setup: add pyproject.toml#67
Merged
utnapischtim merged 11 commits intotu-graz-library:mainfrom Feb 8, 2026
Merged
Conversation
pyproject.toml is needed to build via the build-backend API without, building is specific to setuptools, precluding other backends this prevents generalizing our github-workflow as to allow hatchling
* due to changes in the creation of url it is necessary to set THEME_FRONTPAGE explicitly
utnapischtim
force-pushed
the
feature/pyproject.toml
branch
from
9700fd2 to
0d493d5
Compare
* unsure, but i remember that there was a change in click somewhere which changed the return value? because the output looks normal for calling the group
utnapischtim
force-pushed
the
feature/pyproject.toml
branch
from
0d493d5 to
16fa11c
Compare
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.
pyproject.tomlis needed to build via the build-backend APIwithout it, the building process must be specific to
setuptools, which precludes other backends from being usedthis prevents generalizing our github-workflow to allow use of other backends (e.g.
hatchling)