-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor parsers and support pyproject-only projects #8
Conversation
Refactor the parsers functions into classes, simplify the logic of parsers and add support for projects that only have a `pyproject.toml` file.
💖 Thank you for opening your first pull request in this repository! 💖 A few things to keep in mind:
⭐ No matter what, we are really grateful that you put in the effort to do this! ⭐ |
Raise error if pyproject.toml is missing **and** "build" is a requested source. Otherwise just parse setup.cfg for the other required sources. Rename function.
Test if the function that finds configuration files in disk and decide which sources must be parsed from which file works as expected.
@leouieda would you mind taking a look at this? I want to have this released so I can continue moving Harmonica to There are some coverage lacking in the classes, mostly on errors raised when some sections aren't found in the configuration files. Let me know what do you think about them and if we should write tests for them as well. |
🎉 Congrats on merging your first pull request and welcome to the team! 🎉 If you would like to be added as a author on the Zenodo archive of the next release, add your full name, affiliation, and ORCID (optional) to the We hope that this was a good experience for you. Let us know if there is any way that the contributing process could be improved. |
Refactor the parsers functions into classes, simplify the logic of parsers and add support for projects that only have a
pyproject.toml
file.Relevant issues/PRs:
Dependente was failing when moving Harmonica to
pyproject.toml
only infatiando/harmonica#438
Todo