start using poetry #82
Draft
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
|
Hi Łukasz, thanks so much for this. I haven't used Poetry before and will need to carve out some time to understand it before I merge this, but certainly open to it and appreciative! I will take a look when I have a chance. |
|
sure, if you have any questions etc feel free to ask 👍 |
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.
I have introduced poetry to the project and adjusted
tox.iniand.travis.yml, but generally let's discuss CI and testings topics more deeper in #81, because in my experience well defined CI (either github actions/workflows or travis inimportlintercase) is more valuable thantox, which is from my experience quite hard to use locally and in CI providers