172 migrating from setuppy to pyprojecttoml #173
Merged
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.
Pull Request Template
Description
Pull request addressing #172.
The current use of setup.py for project configuration is becoming outdated and less aligned with modern Python packaging standards. This can lead to potential issues with build isolation, tool interoperability, and future compatibility. Additionally, the imperative nature of setup.py can make it more prone to errors and harder to maintain compared to newer declarative formats.
This pull request entails migration to a
pyproject.toml
file, alongside asetup.cfg
file forflake8
fuctionality and a minimalsetup.py
file for backwards compatability. I have also added in an additional section for the readme to help new contributors develop this project. I have further addedisort
andflake8
support, and fixed all the errors in the codebase.Context of change
Type of change
Please mark any boxes that apply.
How Has This Been Tested?
pip install -e .
andpip install -e '.[dev]'
Checklist: