1
0
mirror of https://github.com/ilri/csv-metadata-quality.git synced 2025-08-12 07:48:07 +02:00
Commit Graph

671 Commits

Author SHA1 Message Date
69b37c612d Merge pull request #81 from ilri/renovate/uv_build-0.x 2025-08-10 20:57:21 +03:00
87978b8bc9 chore(deps): update dependency uv_build to >=0.8.8,<0.9.0 2025-08-10 17:56:23 +00:00
78a5c00636 Merge pull request #80 from ilri/renovate/pandas-2.x 2025-08-10 20:55:25 +03:00
4a6f142800 fix(deps): update dependency pandas to ~=2.3.1 2025-08-10 17:49:15 +00:00
9ed493aa9d Merge pull request #79 from ilri/renovate/python-stdnum-2.x 2025-08-10 20:47:40 +03:00
bb459c963a Merge pull request #78 from ilri/renovate/astral-sh-setup-uv-6.x 2025-08-10 20:44:22 +03:00
23c16c57cb fix(deps): update dependency python-stdnum to v2 2025-08-10 17:44:18 +00:00
11f61342fb chore(deps): update astral-sh/setup-uv action to v6 2025-08-10 17:43:28 +00:00
071c2ac03a CHANGELOG.md: add note about AGROVOC REST API 2025-08-10 20:41:20 +03:00
d051841de0 src: update AGROVOC REST API URL 2025-08-10 20:40:02 +03:00
22b2e3b8ae Update dependencies 2025-07-03 14:37:11 +03:00
be550e21f1 Use uv build backend
uv's build backend expects our module to be in src.

See: https://docs.astral.sh/uv/concepts/build-backend/#modules
2025-07-03 14:33:57 +03:00
753f3340a3 renovate.json: adjust managers
We can apparently use the pep621 manager to manage uv dependencies
now. And we need to disable the pip_requirements manager so the bot
doesn't try to update our requirements.txt file (which is exported
from uv).
2025-04-01 12:55:12 +03:00
188097abe4 Revert "csv_metadata_quality/fix.py: minor logic fix"
This reverts commit b7a81b8ec7.
2025-03-19 16:04:12 +03:00
b7a81b8ec7 csv_metadata_quality/fix.py: minor logic fix
Minor logic fix in missing regions.
2025-02-19 16:01:36 +03:00
8a2c567d1f Version 0.7.0 v0.7.0 2025-01-31 10:12:43 +03:00
42eb9437e3 pyproject.toml: bump a few deps 2025-01-31 10:11:38 +03:00
5400bcb19b Remove pytest-clarity dependency
I think pytest itself has gotten much more readable over the years.
2025-01-31 10:10:33 +03:00
febea54f1b Remove poetry.lock
We switched to rye and then uv, so this is not needed.
2025-01-31 10:03:03 +03:00
b5565124de .github/workflows: fix pytest task 2025-01-30 11:56:27 +03:00
2869919507 pyproject.toml: minimum Python version is 3.10
Apparently this is due to ipython.
2025-01-30 11:55:17 +03:00
f7d66947f7 Use uv instead of rye 2025-01-30 11:55:09 +03:00
1d701f4056 renovate.json: use pep621 manager
We are not using pip requirements files, but I'm wondering if we
need to switch to uv instead.

See: https://docs.renovatebot.com/modules/manager/pep621/
2025-01-30 11:38:49 +03:00
1e339609a6 chore(config): migrate config renovate.json 2025-01-30 11:34:33 +03:00
2b0568de30 .github/workflows: use ubuntu-latest
This is now Ubuntu 24.04.

See: https://github.com/actions/runner-images
2025-01-30 11:28:32 +03:00
9903ada97a pyproject.toml: update isort to v6.0.0 2025-01-30 11:27:51 +03:00
d4b20e282c Python 3.13 2025-01-30 11:27:19 +03:00
9785c18301 Merge pull request #64 from ilri/renovate/ftfy-6.x 2024-10-11 20:02:53 +03:00
de5e292f1a chore(deps): update dependency ftfy to ~=6.3.0 2024-10-11 00:32:38 +00:00
2675cd288e Remove and re-sync rye requirements
Seems there is no way to force rye to sync?
2024-09-26 12:24:36 +03:00
78dc1336d0 requirements-dev.lock: run rye sync 2024-09-26 12:22:09 +03:00
28bbb919ce pyproject.toml: remove fixit from deps
I read about this online and was testing it but never used it.
2024-09-06 15:13:59 +03:00
b1de9552a4 Remove Mjanja CI (drone) 2024-09-06 12:54:16 +03:00
81e3ca3d9c .github/workflows: use rye in CI
Use rye instead of poetry in CI.
2024-08-21 18:56:09 +03:00
c470f8b375 requirements-dev.lock: run rye sync 2024-08-21 17:41:49 +03:00
0f45448517 pyproject.toml: bump dev dependencies 2024-08-21 17:41:36 +03:00
7dd52ca491 requirements: run rye sync 2024-07-29 19:58:42 -07:00
92ff0ee51b Normalize DOIs with %2f
These seem to be incorrectly URL encoded.
2024-06-25 11:54:09 +03:00
ae38a826ec csv_metadata_quality/fix.py: minor update to DOI fix
Normalize www.doi.org to doi.org in DOI field.
2024-06-25 11:48:45 +03:00
c1f630c298 Bump dependencies
All tests passing...
2024-06-18 22:17:38 +03:00
82b056f0ea Use py3langid v0.3.0 2024-06-18 21:51:32 +03:00
7fca981b95 Add .python-version
This was created with:

    rye pin --relaxed cpython@3.12

Rye will now always use the latest 3.12.x apparently.

See: https://rye-up.com/guide/toolchains/
2024-05-23 10:11:10 +03:00
1a9424197b Run rye lock --update-all and rye sync 2024-05-23 10:04:43 +03:00
f6c6c94a1e 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
f500fac64b pyproject.toml: remove scalene from dev deps 2024-05-23 10:00:01 +03:00
8143a7d978 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
94cec080d6 pyproject.toml: remove Hatch direct-references
Apparently I copied this from somewhere but it's not needed in this
project because we are not using direct dependency references (which
seem to be local packages).
2024-05-23 09:43:08 +03:00
9402af1e30 pyproject.toml: add comment about packages
Important for Hatch.
2024-05-23 09:42:11 +03:00
d71ff9082b pyproject.toml: add comment about backend 2024-05-23 09:41:08 +03:00
f309b694c4 Run rye sync to update lockfiles 2024-05-22 23:19:20 +03:00