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.
Unpinned dependency versions cause conflicts, and dependencies should not be left unpinned in the
requirements.txt
file either. Feel free to change the versions as you prefer, but please avoid leaving them unpinned.You can consider using poetry for better dependency management. It provides a lock file and stores the version of every single dependency, including dependencies of other dependencies. Poetry's dependency resolver is better than pip's as well. You can avoid issue like this: #60
I can submit a PR to switch to using
poetry
; however, since it's your app, I won't touch the architecture unless requested. For now, this PR aims to fix immediate problem.I also modified the
.gitignore
because I and probably many others using JetBrains IDEs.Error logs using the default
requirements.txt
Cheers