use poetry for dependency management and build #188
Conversation
This file contains 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
linked docs/development.md as README.md, required for build/realease moved yapf to dev dependencies (from production), added toml for yapf to parse pyproject.toml removed requirements.txt modified run_tests.sh to use poetry required tools from non-slim docker image use bash to utilize alias commands
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://python-poetry.org/docs/
I thought it might be interesting/useful to use poetry to manage deps/builds/project info for the following reasons
poetry buildIf not that's cool too I just thought it would be a fun thing to do, also happy to make any changes requested