alanorth/csv-metadata-quality
1
0
Fork 0
mirror of https://github.com/ilri/csv-metadata-quality.git synced 2024-11-26 15:48:19 +01:00
Code Releases Activity
7edb8b19d7
csv-metadata-quality/requirements-dev.txt

72 lines
2.1 KiB
Plaintext
Raw Normal View History

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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
agate==1.6.1
agate-dbf==0.2.2
agate-excel==0.2.3
agate-sql==0.5.5
appdirs==1.4.4
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
atomicwrites==1.4.0; 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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
attrs==20.3.0
babel==2.9.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
backcall==0.2.0; python_version >= "3.7" and python_version < "4.0"
black==20.8b1
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
certifi==2020.12.5
chardet==4.0.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
click==7.1.2
colorama==0.4.4; python_version >= "3.7" and python_version < "4.0" and sys_platform == "win32" or sys_platform == "win32"
csvkit==1.0.5
dbfread==2.0.7
decorator==4.4.2; python_version >= "3.7" and python_version < "4.0"
et-xmlfile==1.0.1
flake8==3.8.4
idna==2.10
iniconfig==1.1.1
ipython==7.19.0; python_version >= "3.7" and python_version < "4.0"
ipython-genutils==0.2.0; python_version >= "3.7" and python_version < "4.0"
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
isort==5.7.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
jdcal==1.4.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
jedi==0.18.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
langid==1.1.6
leather==0.3.3
mccabe==0.6.1
mypy-extensions==0.4.3
numpy==1.19.4
openpyxl==3.0.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
packaging==20.8
pandas==1.2.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
parsedatetime==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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
parso==0.8.1; python_version >= "3.7" and python_version < "4.0"
pathspec==0.8.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +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"
pluggy==0.13.1
prompt-toolkit==3.0.8; 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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
ptyprocess==0.7.0; python_version >= "3.7" and python_version < "4.0" and sys_platform != "win32"
py==1.10.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
pycodestyle==2.6.0
pycountry==19.8.18
pyflakes==2.2.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
pygments==2.7.3; 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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
pyparsing==2.4.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
pytest==6.2.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
pytest-clarity==0.3.0a0
python-dateutil==2.8.1
python-slugify==4.0.1
python-stdnum==1.14
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
pytz==2020.5
regex==2020.11.13
requests==2.25.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
requests-cache==0.5.2
six==1.15.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
sqlalchemy==1.3.22
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
termcolor==1.1.0
text-unidecode==1.3
toml==0.10.2
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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
typed-ast==1.4.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
typing-extensions==3.7.4.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2021-01-03 14:42:00 +01:00
urllib3==1.26.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 on Python 3.6 in Travis: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.
2020-11-03 06:42:45 +01:00
wcwidth==0.2.5; python_version >= "3.7" and python_version < "4.0"
xlrd==1.2.0
Copy Permalink