alanorth/csv-metadata-quality
1
0
Fork 0
mirror of https://github.com/ilri/csv-metadata-quality.git synced 2024-11-17 19:47:03 +01:00
Code Releases Activity
b1de9552a4
csv-metadata-quality/pyproject.toml

65 lines
1.7 KiB
TOML
Raw Normal View History

pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02: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 16:31:36 +02:00
name = "csv-metadata-quality"
Version 0.6.1
2023-02-23 11:46:56 +01:00
version = "0.6.1"
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."
pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02: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 08:44:16 +02:00
license= { file = "LICENSE.txt" }
pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02:00
dependencies = [
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 09:01:46 +02:00
"pandas[feather,performance]~=2.2",
Bump dependencies All tests passing...
2024-06-18 21:17:38 +02:00
"python-stdnum~=1.20",
"requests~=2.32",
"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 09:01:46 +02:00
"colorama~=0.4",
Bump dependencies All tests passing...
2024-06-18 21:17:38 +02:00
"ftfy~=6.2.0",
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 09:01:46 +02:00
"country-converter~=1.2",
Bump dependencies All tests passing...
2024-06-18 21:17:38 +02:00
"pycountry~=24.6.1",
Use py3langid v0.3.0
2024-06-18 20:51:32 +02:00
"py3langid~=0.3",
pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02:00
]
readme = "README.md"
requires-python = ">= 3.9"
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
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 08:44:16 +02:00
classifiers = [
"License :: OSI Approved :: GNU General Public License v3 (GPLv3)",
"Natural Language :: English",
"Operating System :: OS Independent",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
"Programming Language :: Python :: 3.12",
"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 21:02:05 +02: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 08:49:43 +01:00
csv-metadata-quality = 'csv_metadata_quality.__main__:main'
pyproject.toml: add comment about backend
2024-05-23 08:41:08 +02:00
# So rye doesn't fall back to setuptools
# 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 21:02:05 +02: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 16:31:36 +02:00
pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02:00
[tool.rye]
managed = true
dev-dependencies = [
pyproject.toml: bump dev dependencies
2024-08-21 16:41:36 +02:00
"pytest~=8.3",
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 09:01:46 +02:00
"pytest-clarity~=1.0",
"isort~=5.13",
pyproject.toml: bump dev dependencies
2024-08-21 16:41:36 +02:00
"csvkit~=2.0",
"ipython~=8.26",
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 09:01:46 +02:00
"fixit~=2.1",
pyproject.toml: update formatting rye requires a slightly different formatting.
2024-04-14 21:02:05 +02:00
]
pyproject.toml: add ipython to dev dependencies
2022-11-28 15:11:18 +01:00
pyproject.toml: add comment about packages Important for Hatch.
2024-05-23 08:42:11 +02: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 21:02:05 +02: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 14:03:10 +01:00
[tool.isort]
profile = "black"
line_length=88
Copy Permalink