pyproject.toml and CI #4
Open
Conversation
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
1 participant
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 pull request includes significant changes to automate the build and publish process for the project across multiple architectures and to define the project's build system and dependencies using
pyproject.toml. The most important changes are as follows:Automation of build and publish process:
.github/workflows/wheels.yml: Added a GitHub Actions workflow to build and publish wheels for multiple architectures. This includes steps for setting up Python, installing dependencies, building wheels, and uploading artifacts. Additionally, it includes a job to publish the package to PyPI when a new release is created.Project build system and dependencies:
pyproject.toml: Introduced apyproject.tomlfile to define the build system requirements, project metadata, dependencies, and setuptools configuration. This includes specifying the build backend, project details, and package information.