alanorth/csv-metadata-quality
1
0
Fork 0
mirror of https://github.com/ilri/csv-metadata-quality.git synced 2024-11-29 09:08:26 +01:00
Code Releases Activity
41b813be6e
csv-metadata-quality/pyproject.toml

39 lines
992 B
TOML
Raw Normal View History

Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
[tool.poetry]
name = "csv-metadata-quality"
Bump version to 0.6.0-dev
2021-12-09 22:21:30 +01:00
version = "0.6.0-dev"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
description="A simple, but opinionated CSV quality checking and fixing pipeline for CSVs in the DSpace ecosystem."
authors = ["Alan Orth <alan.orth@gmail.com>"]
pyproject.toml: Update license specifier We need to use valid SPDX license identifiers.
2020-06-09 13:22:53 +02:00
license="GPL-3.0-only"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
repository = "https://github.com/ilri/csv-metadata-quality"
homepage = "https://github.com/ilri/csv-metadata-quality"
pyproject.toml: Add csv-metadata-quality as a script For some reason I stopped having csv-metadata-quality available in my poetry environment after install. It seems I need to add it as a poetry tool script? I had already done this in setup.py years ago, which works for regular python setup.py installs, but hadn't needed to do it in poetry for a year or more that I've been using it, until now.
2021-03-08 08:49:43 +01:00
[tool.poetry.scripts]
csv-metadata-quality = 'csv_metadata_quality.__main__:main'
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
[tool.poetry.dependencies]
pyproject.toml: bump Pandas to v1.4.0 As of Pandas v1.4.0 the minimum Python version is 3.8. See: https://pandas.pydata.org/docs/whatsnew/v1.4.0.html
2022-01-30 11:03:13 +01:00
python = "^3.8"
pandas = "^1.4.0"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
python-stdnum = "^1.13"
xlrd = "^1.2.0"
pyproject.toml: update requests and requests-cache
2022-01-30 11:11:01 +01:00
requests = "^2.27.1"
requests-cache = "^0.9.1"
pyproject.toml: update pycountry Seems to be a few major versions from 19.x.x to 21.x.x. All tests passing in pytest so it's probably fine.
2022-01-30 11:15:38 +01:00
pycountry = "^22.1.10"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
langid = "^1.1.6"
Add colorama for colored output Red for errors, yellow for warnings or information, and green for fixes.
2021-02-21 12:00:31 +01:00
colorama = "^0.4.4"
Add validation of SPDX license identifiers Currently this only checks the dcterms.license field and the result will only be a warning.
2021-03-11 09:33:16 +01:00
spdx-license-list = "^0.5.2"
pyproject.toml: use ftfy 6.0 Lots of improvements here! Improvements to heuristics and a new way to configure which fixes get applied. See: https://github.com/rspeer/python-ftfy/blob/master/CHANGELOG.md#version-60-april-2-2021
2021-12-15 20:48:56 +01:00
ftfy = "^6.0"
pyproject.toml: limit SQLAlchemy to < 1.4.23 SQLAlchemy gets pulled in by csvkit's agate-sql dependency and there is currently an issue with Poetry's parsing of the SQLAlchemy 1.4.23 constraints. Temporarily explicitly install a version of SQLAlchemy that works (can remove later once Poetry fixes this). Anyways, I am not using any SQLAlchemy features that I know of. See: https://github.com/python-poetry/poetry/issues/4402
2021-09-06 20:01:09 +02:00
SQLAlchemy = ">=1.3.3,<1.4.23"
Add check for countries without matching regions If we have country "Kenya" we should have region "Eastern Africa" according to the UN M.49 geolocation scheme.
2021-12-08 14:02:20 +01:00
country-converter = "^0.7.4"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
[tool.poetry.dev-dependencies]
Update poetry package dependencies
2020-10-06 16:20:16 +02:00
pytest = "^6.1.1"
pyproject.toml: bump flake8
2022-01-30 11:21:09 +01:00
flake8 = "^4.0.1"
pyproject.toml: Update pytest-clarity and black These seem to have much newer versions that didn't get updated in this project due to the version pinning selector I was using with poetry. In the case of pytest-clarity the previous version was 0.3.1 and the version selector was a caret (^), which will never update the left-most (major) number. Now they seem to be on 1.x.x so it will be OK in the future. In the case of black, they use weird numbering so it's anyone's guess how this will work! Luckily it's only used for linting and formatting.
2021-07-06 14:30:41 +02:00
pytest-clarity = "^1.0.1"
pyproject.toml: update black It's no longer in beta!
2022-01-30 11:22:47 +01:00
black = "^22.1.0"
Update poetry package dependencies
2020-10-06 16:20:16 +02:00
isort = "^5.5.4"
Add poetry project file and lock 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.
2020-05-31 16:31:36 +02:00
csvkit = "^1.0.5"
[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"
Copy Permalink