292 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Alan Orth	d76e72532a	Move unreleased changes to v0.4.4	2021-02-21 13:25:22 +02:00
Alan Orth	13980d2dde	CHANGELOG.md: Add note about colored output	2021-02-21 13:12:26 +02:00
Alan Orth	9aaaa62461	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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.	2021-02-21 13:10:52 +02:00
Alan Orth	a7fc5a246c	Colorize output ... Messages will be colorized: - Red for errors - Yellow for warnings or information - Green for fixes	2021-02-21 13:01:25 +02:00
Alan Orth	7fb8acb866	Add colorama for colored output ... Red for errors, yellow for warnings or information, and green for fixes.	2021-02-21 13:00:31 +02:00
Alan Orth	9f5d2c2c4f	poetry.lock: Run poetry update	2021-02-15 15:13:12 +02:00
Alan Orth	202abf140c	CHANGELOG.md: Add note about poetry	2021-02-04 21:48:12 +02:00
Alan Orth	0cd6d3dfe6	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 in CI: ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==.	2021-02-04 21:46:49 +02:00
Alan Orth	a458beac55	poetry.lock: Run poetry update	2021-02-04 21:45:30 +02:00
Alan Orth	e62ecb0a8f	CHANGELOG.md: Add note about new date format	2021-02-04 21:43:44 +02:00
Alan Orth	de92f32ab6	csv_metadata_quality/check.py: More date formats ... We should also allow ISO 8601 extended in combined date and time format. DSpace does not have a problem with dates in this format and I have found some metadata that uses this date format. For example: 2020-08-31T11:04:56Z See: https://en.wikipedia.org/wiki/ISO_8601	2021-02-04 21:39:14 +02:00
Alan Orth	dbbbc0944a	README.md: Add handle to citation	2021-01-27 10:33:37 +02:00
Alan Orth	d17bf3033c	README.md: Add citation	2021-01-27 10:32:26 +02:00
Alan Orth	2ec52f1b73	README.md: Update description	2021-01-26 15:43:41 +02:00
Alan Orth	aa1abf15a7	README.md: Adjust title	2021-01-26 15:35:21 +02:00
Alan Orth	cbf94490f2	Version 0.4.3	2021-01-26 15:22:40 +02:00
Alan Orth	f3d0d5ef07	setup.py: Remove Python 3.6 ... I actually removed Python 3.6 support a few weeks ago after updating to Pandas 1.2.0, but forgot to update this.	2021-01-26 15:22:08 +02:00
Alan Orth	4b7b99c94c	CHANGELOG.md: Add note about multi-value separators	2021-01-26 15:20:22 +02:00
Alan Orth	df670e81b9	README.md: Use badge from my Drone CI ... I'm not using SourceHut anymore.	2021-01-26 14:38:50 +02:00
Alan Orth	ae357d8c6c	Revert "Update requirements" ... This reverts commit ca80340f7a. Nope, we still need the --without-hashes because this still fails on Python 3.7, but not 3.8 or 3.9. From looking around it seems that nobody can agree whether poetry should handle this, pip should handle it, or upstream projects should pin their dependencies.	2021-01-26 14:15:31 +02:00
Alan Orth	ca80340f7a	Update requirements ... Generated with poetry export: $ poetry export -f requirements.txt > requirements.txt $ poetry export --dev -f requirements.txt > requirements-dev.txt Trying to see if we no longer need --without-hashes since we don't support Python 3.6 anymore.	2021-01-26 11:46:05 +02:00
Alan Orth	cc1743b86d	Remove .build.yml ... I will just use GitHub Actions and Drone.	2021-01-26 11:41:30 +02:00
Alan Orth	bcb9885c6b	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-26 10:36:48 +02:00
Alan Orth	b484b75178	poetry.lock: Run poetry update	2021-01-26 10:36:04 +02:00
Alan Orth	d3880a9dfa	Remove Python 3.6 support ... Pandas 1.2.0 apparently requires Python 3.7.1+.	2021-01-03 15:51:53 +02:00
Alan Orth	7edb8b19d7	tests/test_check.py: Reformat with black	2021-01-03 15:50:21 +02:00
Alan Orth	a6709c7f82	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 15:42:00 +02:00
Alan Orth	d489ea4609	poetry.lock: Run poetry update	2021-01-03 15:41:08 +02:00
Alan Orth	96634cbb67	pytest.ini: Change --strict to --strict-markers ... This is deprecated since pytest 6.2.0. See: https://docs.pytest.org/en/stable/deprecations.html#the-strict-command-line-option	2021-01-03 15:40:14 +02:00
Alan Orth	29e67a0887	Add tests for unnecessary multi-value separators	2021-01-03 15:37:18 +02:00
Alan Orth	32cea2055f	data/test.csv: Add unnecessary multi-value separator	2021-01-03 15:33:04 +02:00
Alan Orth	0dc66c5c4e	Expand check/fix for multi-value separators ... I just came across some metadata that had unnecessary multi-value separators at the end of a field, causing a blank value to be used. For example: "Kenya||Tanzania||"	2021-01-03 15:30:03 +02:00
Alan Orth	c26ad83534	.github: Test CLI invocation	2020-12-14 23:47:09 +02:00
Alan Orth	72ca9d99bf	setup.py: Add Python 3.9 ... [SKIP CI]	2020-12-14 23:44:35 +02:00
Alan Orth	ae33a9b793	Add .drone.yml	2020-12-14 23:42:23 +02:00
Alan Orth	fc0367bfc8	README.md: Update note about Python version	2020-12-08 10:52:24 +02:00
Alan Orth	e33b285034	README.md: Add GitHub Actions badge	2020-12-08 10:48:31 +02:00
Alan Orth	349fca03b8	.github/workflows/python-app.yml: Rename ... This name is displayed in the badge so it should be something more relevant.	2020-12-08 10:46:39 +02:00
Alan Orth	52d8904870	Remove .travis.yml ... They changed their free tier and I might as well use GitHub Actions for ILRI stuff anyways.	2020-12-08 10:41:36 +02:00
Alan Orth	971c69e535	Create python-app.yml ... Try GitHub Actions for Python 3.8 using GitHub's Python example.	2020-12-08 10:38:52 +02:00
Alan Orth	f8cc233e25	.travis.yml: Use Amazon Graviton2 ARM environment ... These are the new hotness and should have faster build times. See: https://blog.travis-ci.com/2020-09-11-arm-on-aws	2020-12-06 10:49:03 +02:00
Alan Orth	aa7b7a9592	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 07:42:45 +02:00
Alan Orth	57b455bde7	poetry.lock: Run poetry update	2020-11-03 07:40:56 +02:00
Alan Orth	23b95fa368	.travis.yml: Use Ubuntu 20.04 "Focal" environment	2020-10-29 00:14:54 +03:00
Alan Orth	6985f76aa3	.travis.yml: Bump Python versions ... Test Python 3.9 now that it was released, and allow tests to fail on nightly builds.	2020-10-29 00:14:36 +03:00
Alan Orth	98a6a19e12	Update requirements-dev.txt ... Generated with poetry export: $ poetry export --dev -f requirements.txt > requirements-dev.txt	2020-10-06 17:48:46 +03:00
Alan Orth	f4914c414f	Only install ipython on Python 3.7+	2020-10-06 17:48:16 +03:00
Alan Orth	d352fe8017	Update requirements ... Generated with poetry export: $ poetry export -f requirements.txt > requirements.txt $ poetry export --dev -f requirements.txt > requirements-dev.txt	2020-10-06 17:21:33 +03:00
Alan Orth	f13c360084	Update poetry package dependencies	2020-10-06 17:20:16 +03:00
Alan Orth	7cfd4c0b59	csv_metadata_quality: Move scoped imports to global ... According to PEP8 we should avoid scoped imports unless you have a good reason. Here there are two cases where we do (issn and isbn), but I will move the others to the global scope.	2020-10-06 17:11:39 +03:00