Generated with poetry export:
$ poetry export -f requirements.txt > requirements.txt
$ poetry export --dev -f requirements.txt > requirements-dev.txt
Trying to see if we no longer need --without-hashes since we don't
support Python 3.6 anymore.
Generated with poetry export:
$ poetry export --without-hashes -f requirements.txt > requirements.txt
$ poetry export --without-hashes --dev -f requirements.txt > requirements-dev.txt
I am trying `--without-hashes` to work around an error on pip install
when running on Python 3.6 in Travis:
ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
Generated with poetry export:
$ poetry export --without-hashes -f requirements.txt > requirements.txt
$ poetry export --without-hashes --dev -f requirements.txt > requirements-dev.txt
I am trying `--without-hashes` to work around an error on pip install
when running on Python 3.6 in Travis:
ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
I just came across some metadata that had unnecessary multi-value
separators at the end of a field, causing a blank value to be used.
For example: "Kenya||Tanzania||"
Generated with poetry export:
$ poetry export --without-hashes -f requirements.txt > requirements.txt
$ poetry export --without-hashes --dev -f requirements.txt > requirements-dev.txt
I am trying `--without-hashes` to work around an error on pip install
when running on Python 3.6 in Travis:
ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
According to PEP8 we should avoid scoped imports unless you have a
good reason. Here there are two cases where we do (issn and isbn),
but I will move the others to the global scope.
List of updated modules:
- Updating numpy (1.19.1 -> 1.19.2)
- Updating pygments (2.6.1 -> 2.7.1)
- Updating pandas (1.1.1 -> 1.1.2)
All tests still pass according to pytest.
I want to try to use poetry instead of pipenv because pipenv takes
forever to do dependency resolution sometimes. Also, I have had a
few issues with Python modules like black that don't have releases
other than pre-releases, and even including the project itself in
the dependencies (pip install -e . ...?). My initial experience is
that poetry handles this better.