csv-metadata-quality/pyproject.toml

[project]
name = "csv-metadata-quality"
version = "0.7.0"
description="A simple, but opinionated CSV quality checking and fixing pipeline for CSVs in the DSpace ecosystem."
authors = [
    { name = "Alan Orth", email = "alan.orth@gmail.com" }
]
license= { file = "LICENSE.txt" }
dependencies = [
    "pandas[feather,performance]~=2.2.3",
    "python-stdnum~=1.20",
    "requests~=2.32.3",
    "requests-cache~=1.2.1",
    "colorama~=0.4",
    "ftfy~=6.3.0",
    "country-converter~=1.3",
    "pycountry~=24.6.1",
    "py3langid~=0.3",
]
readme = "README.md"
requires-python = ">= 3.10"

classifiers = [
  "License :: OSI Approved :: GNU General Public License v3 (GPLv3)",
  "Natural Language :: English",
  "Operating System :: OS Independent",
  "Programming Language :: Python :: 3.10",
  "Programming Language :: Python :: 3.11",
  "Programming Language :: Python :: 3.12",
  "Programming Language :: Python :: 3.13",
  "Programming Language :: Python :: Implementation :: CPython",
]

[project.urls]
repository = "https://github.com/ilri/csv-metadata-quality"
homepage = "https://github.com/ilri/csv-metadata-quality"

[project.scripts]
csv-metadata-quality = 'csv_metadata_quality.__main__:main'

# So uv doesn't fall back to setuptools
# See: https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-build-backend
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[dependency-groups]
dev = [
    "pytest~=8.3",
    "isort~=6.0",
    "csvkit~=2.0",
    "ipython~=8.31",
]

# So hatch doesn't try to build other top-level directories like "data"
[tool.hatch.build.targets.wheel]
packages = ["csv_metadata_quality"]

[tool.isort]
profile = "black"
line_length=88
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`[project]`
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 17:31:36 +03:00			`name = "csv-metadata-quality"`
Version 0.7.0 2025-01-31 10:12:43 +03:00			`version = "0.7.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 17:31:36 +03:00			`description="A simple, but opinionated CSV quality checking and fixing pipeline for CSVs in the DSpace ecosystem."`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`authors = [`
			`{ name = "Alan Orth", email = "alan.orth@gmail.com" }`
			`]`
pyproject.toml: align better with PEP 621 This PEP was approved years ago and has become a standard for the way pyproject.toml file is laid out. We need to make some changes to the license, URLs, add classifiers, etc. See: https://peps.python.org/pep-0621/ 2024-05-23 09:44:16 +03:00			`license= { file = "LICENSE.txt" }`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`dependencies = [`
pyproject.toml: bump a few deps 2025-01-31 10:11:38 +03:00			`"pandas[feather,performance]~=2.2.3",`
Bump dependencies All tests passing... 2024-06-18 22:17:38 +03:00			`"python-stdnum~=1.20",`
pyproject.toml: bump a few deps 2025-01-31 10:11:38 +03:00			`"requests~=2.32.3",`
Bump dependencies All tests passing... 2024-06-18 22:17:38 +03:00			`"requests-cache~=1.2.1",`
pyproject.toml: use ~= for dependencies These are the closest to semantic versioning in Python that I can find with PEP 621 syntax. For example: > ~=3.1: version 3.1 or later, but not version 4.0 or later. > ~=3.1.2: version 3.1.2 or later, but not version 3.2.0 or later. For most cases I want to bump the minor and micro / patch. See: https://packaging.python.org/en/latest/specifications/version-specifiers/#examples 2024-05-23 10:01:46 +03:00			`"colorama~=0.4",`
chore(deps): update dependency ftfy to ~=6.3.0 2024-10-11 00:32:38 +00:00			`"ftfy~=6.3.0",`
pyproject.toml: bump a few deps 2025-01-31 10:11:38 +03:00			`"country-converter~=1.3",`
Bump dependencies All tests passing... 2024-06-18 22:17:38 +03:00			`"pycountry~=24.6.1",`
Use py3langid v0.3.0 2024-06-18 21:51:32 +03:00			`"py3langid~=0.3",`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`]`
			`readme = "README.md"`
pyproject.toml: minimum Python version is 3.10 Apparently this is due to ipython. 2025-01-30 11:55:17 +03:00			`requires-python = ">= 3.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 17:31:36 +03:00
pyproject.toml: align better with PEP 621 This PEP was approved years ago and has become a standard for the way pyproject.toml file is laid out. We need to make some changes to the license, URLs, add classifiers, etc. See: https://peps.python.org/pep-0621/ 2024-05-23 09:44:16 +03:00			`classifiers = [`
			`"License :: OSI Approved :: GNU General Public License v3 (GPLv3)",`
			`"Natural Language :: English",`
			`"Operating System :: OS Independent",`
			`"Programming Language :: Python :: 3.10",`
			`"Programming Language :: Python :: 3.11",`
			`"Programming Language :: Python :: 3.12",`
Python 3.13 2025-01-30 11:27:19 +03:00			`"Programming Language :: Python :: 3.13",`
pyproject.toml: align better with PEP 621 This PEP was approved years ago and has become a standard for the way pyproject.toml file is laid out. We need to make some changes to the license, URLs, add classifiers, etc. See: https://peps.python.org/pep-0621/ 2024-05-23 09:44:16 +03:00			`"Programming Language :: Python :: Implementation :: CPython",`
			`]`

			`[project.urls]`
			`repository = "https://github.com/ilri/csv-metadata-quality"`
			`homepage = "https://github.com/ilri/csv-metadata-quality"`

pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`[project.scripts]`
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 09:49:43 +02:00			`csv-metadata-quality = 'csv_metadata_quality.__main__:main'`

Use uv instead of rye 2025-01-30 11:55:09 +03:00			`# So uv doesn't fall back to setuptools`
pyproject.toml: add comment about backend 2024-05-23 09:41:08 +03:00			`# See: https://packaging.python.org/en/latest/tutorials/packaging-projects/#choosing-build-backend`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`[build-system]`
			`requires = ["hatchling"]`
			`build-backend = "hatchling.build"`
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 17:31:36 +03:00
Use uv instead of rye 2025-01-30 11:55:09 +03:00			`[dependency-groups]`
			`dev = [`
pyproject.toml: bump dev dependencies 2024-08-21 17:41:36 +03:00			`"pytest~=8.3",`
pyproject.toml: update isort to v6.0.0 2025-01-30 11:27:38 +03:00			`"isort~=6.0",`
pyproject.toml: bump dev dependencies 2024-08-21 17:41:36 +03:00			`"csvkit~=2.0",`
pyproject.toml: bump a few deps 2025-01-31 10:11:38 +03:00			`"ipython~=8.31",`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`]`
pyproject.toml: add ipython to dev dependencies 2022-11-28 17:11:18 +03:00
pyproject.toml: add comment about packages Important for Hatch. 2024-05-23 09:42:11 +03:00			`# So hatch doesn't try to build other top-level directories like "data"`
pyproject.toml: update formatting rye requires a slightly different formatting. 2024-04-14 22:02:05 +03:00			`[tool.hatch.build.targets.wheel]`
			`packages = ["csv_metadata_quality"]`
Move isort config to pyproject.toml See: https://pycqa.github.io/isort/docs/configuration/black_compatibility.html 2022-12-20 15:03:10 +02:00
			`[tool.isort]`
			`profile = "black"`
			`line_length=88`