Use pyproject.toml for project metadata and build-system #1077
+62
−92
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 modernises this project to use pyproject.toml as supported by setuptools to handle project metadata (PEP 621) and define the build-system.
Modern tools like uv can benefit from this PR.
Other changes:
gempy/_version.pyauthor_email, as it does not have a 1:1 author:email; if one or more emails want to be assigned to the table, this can be done easily (in this PR or subsequent)-r requirements.txtsyntax is not supported by setuptools' dynamic functions, so is commented out -- I suggest migrating from these files to embedding requirements into pyproject.tomlsetuptools.packages.findfrom the "exclude" strategy to the "include" strategy, to prevent accidentally including other directories.