alanorth/csv-metadata-quality
1
0
Fork 0
mirror of https://github.com/ilri/csv-metadata-quality.git synced 2024-11-10 16:25:45 +01:00
Code Releases Activity
46098861ed
csv-metadata-quality/requirements-dev.txt

73 lines
5.7 KiB
Plaintext
Raw Normal View History

Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
agate-dbf==0.2.2
agate-excel==0.2.3
agate-sql==0.5.5
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-11 10:11:19 +01:00
agate==1.6.2
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
appdirs==1.4.4; python_version >= "3.6"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
appnope==0.1.2; python_version >= "3.7" and python_version < "4.0" and sys_platform == "darwin"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
atomicwrites==1.4.0; python_version >= "3.6" and python_full_version < "3.0.0" and sys_platform == "win32" and (python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6") or sys_platform == "win32" and python_version >= "3.6" and python_full_version >= "3.4.0" and (python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6")
attrs==20.3.0; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
babel==2.9.0; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
backcall==0.2.0; python_version >= "3.7" and python_version < "4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
black==20.8b1; python_version >= "3.6"
certifi==2020.12.5; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0"
chardet==4.0.0; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0"
click==7.1.2; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.5.0" and python_version >= "3.6"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-21 12:10:52 +01:00
colorama==0.4.4; (python_version >= "2.7" and python_full_version < "3.0.0") or (python_full_version >= "3.5.0")
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
csvkit==1.0.5
dbfread==2.0.7
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
decorator==4.4.2; python_version >= "3.7" and python_full_version < "3.0.0" and python_version < "4.0" or python_version >= "3.7" and python_version < "4.0" and python_full_version >= "3.2.0"
et-xmlfile==1.0.1; python_version >= "3.6"
flake8==3.8.4; (python_version >= "2.7" and python_full_version < "3.0.0") or (python_full_version >= "3.4.0")
idna==2.10; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0"
iniconfig==1.1.1; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
ipython-genutils==0.2.0; python_version >= "3.7" and python_version < "4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-04 20:33:33 +01:00
ipython==7.21.0; python_version >= "3.7" and python_version < "4.0"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
isodate==0.6.0
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
isort==5.7.0; python_version >= "3.6" and python_version < "4.0"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
jedi==0.18.0; python_version >= "3.7" and python_version < "4.0"
langid==1.1.6
leather==0.3.3
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
mccabe==0.6.1; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
mypy-extensions==0.4.3; python_version >= "3.6"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-21 12:10:52 +01:00
numpy==1.20.1; python_version >= "3.7" and python_full_version >= "3.7.1"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-11 10:11:19 +01:00
openpyxl==3.0.7; python_version >= "3.6"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
packaging==20.9; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-04 20:33:33 +01:00
pandas==1.2.3; python_full_version >= "3.7.1"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
parsedatetime==2.6
parso==0.8.1; python_version >= "3.7" and python_version < "4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
pathspec==0.8.1; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.5.0" and python_version >= "3.6"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
pexpect==4.8.0; python_version >= "3.7" and python_version < "4.0" and sys_platform != "win32"
pickleshare==0.7.5; python_version >= "3.7" and python_version < "4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
pluggy==0.13.1; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-21 12:10:52 +01:00
prompt-toolkit==3.0.16; python_version >= "3.7" and python_version < "4.0" and python_full_version >= "3.6.1"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
ptyprocess==0.7.0; python_version >= "3.7" and python_version < "4.0" and sys_platform != "win32"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
py==1.10.0; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
pycodestyle==2.6.0; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
pycountry==19.8.18
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
pyflakes==2.2.0; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-11 10:11:19 +01:00
pygments==2.8.1; python_version >= "3.7" and python_version < "4.0"
pyicu==2.6
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
pyparsing==2.4.7; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
pytest-clarity==0.3.0a0; (python_version >= "2.7" and python_full_version < "3.0.0") or (python_full_version >= "3.4.0")
pytest==6.2.2; python_version >= "3.6"
python-dateutil==2.8.1; python_full_version >= "3.7.1"
python-slugify==4.0.1; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-21 12:10:52 +01:00
python-stdnum==1.16
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
pytimeparse==1.1.8
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
pytz==2021.1; python_full_version >= "3.7.1"
regex==2020.11.13; python_version >= "3.6"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
requests-cache==0.5.2
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
requests==2.25.1; (python_version >= "2.7" and python_full_version < "3.0.0") or (python_full_version >= "3.5.0")
six==1.15.0; python_full_version >= "3.7.1"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-03-11 10:11:19 +01:00
spdx-license-list==0.5.2
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
sqlalchemy==1.3.23; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
termcolor==1.1.0; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.4.0"
text-unidecode==1.3; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0"
toml==0.10.2; python_version >= "3.6" and python_full_version < "3.0.0" or python_full_version >= "3.4.0" and python_version >= "3.6"
Revert "Update requirements" This reverts commit ca80340f7a717a9c8cd1780ba12e5bd366c9900d. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.
2021-01-26 13:15:31 +01:00
traitlets==5.0.5; python_version >= "3.7" and python_version < "4.0"
Update requirements 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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-02-04 20:46:49 +01:00
typed-ast==1.4.2; python_version >= "3.6"
typing-extensions==3.7.4.3; python_version >= "3.6"
urllib3==1.26.3; python_version >= "2.7" and python_full_version < "3.0.0" or python_full_version >= "3.5.0" and python_version < "4"
wcwidth==0.2.5; python_version >= "3.7" and python_version < "4.0" and python_full_version >= "3.6.1"
xlrd==1.2.0; (python_version >= "2.7" and python_full_version < "3.0.0") or (python_full_version >= "3.4.0")
Copy Permalink