Bump pytest from 8.4.1 to 9.0.2 (#51)

dependabot[bot] · docktermj · web-flow · commit 4b9ff664e885 · 2026-01-14T11:46:51.000-05:00
* Bump pytest from 8.4.1 to 9.0.2 Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.4.1 to 9.0.2. - [Release notes](https://github.com/pytest-dev/pytest/releases) - [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pytest@8.4.1...9.0.2) --- updated-dependencies: - dependency-name: pytest dependency-version: 9.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> * Update to template --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: docktermj <michael@dockter.com>
diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
@@ -0,0 +1,47 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+This is **mapper-base**, a Python library providing base utilities for Senzing data mappers. It's used as a dependency by higher-level mapper projects (mapper-ijic, mapper-dowjones, etc.) for entity resolution tasks.
+
+The `base_library` class in `src/base_mapper.py` provides:
+
+- Date formatting and normalization (`formatDate`)
+- ISO country/state code conversion (`isoCountryCode`, `isoStateCode`)
+- Company vs person name detection (`isCompanyName`)
+- Statistics tracking (`updateStat`)
+
+Lookup tables in `src/base_variants.json` contain mappings for state codes, country codes, organization tokens, and person tokens.
+
+## Development Commands
+
+**Install all dependencies (development, testing, linting, docs):**
+
+```bash
+python -m pip install --group all .
+```
+
+**Run pylint:**
+
+```bash
+pylint $(git ls-files '*.py' ':!:docs/source/*')
+```
+
+**Run a single Python file directly:**
+
+```bash
+python src/base_mapper.py
+```
+
+## Code Style
+
+- **Line length**: 120 characters
+- **Formatter**: Black with `line-length = 120`
+- **Import sorting**: isort with "black" profile
+- **Linting**: Pylint with relaxed rules (see `.pylintrc` for disabled checks including `missing-module-docstring`, `missing-function-docstring`, `invalid-name`, `line-too-long`)
+
+## Python Version Support
+
+Python 3.10, 3.11, 3.12, and 3.13 are supported and tested in CI.
diff --git a/.claude/commands/senzing-code-review.md b/.claude/commands/senzing-code-review.md
diff --git a/.claude/commands/senzing.md b/.claude/commands/senzing.md
@@ -0,0 +1,3 @@
+# Senzing
+
+- Perform the steps specified by <https://raw.githubusercontent.com/senzing-factory/claude/refs/tags/v1/commands/senzing.md>
diff --git a/.claude/settings.json b/.claude/settings.json
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -1,4 +1,4 @@
- # Default code owner
+# Default code owner
 
 * @Senzing/senzing-mappers
 
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -3,11 +3,15 @@
 
 version: 2
 updates:
-  - package-ecosystem: "github-actions"
-    directory: "/"
+  - package-ecosystem: github-actions
+    cooldown:
+      default-days: 21
+    directory: /
     schedule:
-      interval: "daily"
-  - package-ecosystem: "pip"
-    directory: "/"
+      interval: daily
+  - package-ecosystem: pip
+    cooldown:
+      default-days: 21
+    directory: /
     schedule:
-      interval: "daily"
+      interval: daily
diff --git a/.github/workflows/add-labels-standardized.yaml b/.github/workflows/add-labels-standardized.yaml
@@ -1,4 +1,4 @@
-name: add labels standardized
+name: Add labels standardized
 
 on:
   issues:
diff --git a/.github/workflows/add-to-project-senzing-dependabot.yaml b/.github/workflows/add-to-project-senzing-dependabot.yaml
@@ -1,4 +1,4 @@
-name: add to project senzing github organization dependabot
+name: Add to project senzing github organization dependabot
 
 on:
   pull_request:
diff --git a/.github/workflows/add-to-project-senzing.yaml b/.github/workflows/add-to-project-senzing.yaml
@@ -1,4 +1,4 @@
-name: add to project senzing github organization
+name: Add to project senzing github organization
 
 on:
   issues:
diff --git a/.github/workflows/claude-pr-review.yaml b/.github/workflows/claude-pr-review.yaml
@@ -1,13 +1,13 @@
 name: Claude PR Review
 
-concurrency:
-  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
-  cancel-in-progress: true
-
 on:
   pull_request:
     types: [opened, synchronize]
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
 permissions: {}
 
 jobs:
diff --git a/.github/workflows/dependabot-approve-and-merge.yaml b/.github/workflows/dependabot-approve-and-merge.yaml
@@ -4,6 +4,10 @@ on:
   pull_request:
     branches: [main]
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
 permissions: {}
 
 jobs:
diff --git a/.github/workflows/lint-workflows.yaml b/.github/workflows/lint-workflows.yaml
@@ -1,11 +1,13 @@
-name: lint workflows
+name: Lint workflows
 
 on:
-  push:
-    branches-ignore: [main]
   pull_request:
     branches: [main]
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
 permissions: {}
 
 jobs:
diff --git a/.github/workflows/move-pr-to-done-dependabot.yaml b/.github/workflows/move-pr-to-done-dependabot.yaml
@@ -1,4 +1,4 @@
-name: move pr to done dependabot
+name: Move pr to done dependabot
 
 on:
   pull_request:
diff --git a/.github/workflows/pylint.yaml b/.github/workflows/pylint.yaml
@@ -1,6 +1,12 @@
-name: pylint
+name: Pylint
 
-on: [push]
+on:
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
 
 permissions: {}
 
@@ -12,8 +18,10 @@ jobs:
       contents: read
     runs-on: ubuntu-latest
     strategy:
+      fail-fast: false
       matrix:
-        python-version: ["3.9", "3.10", "3.11", "3.12"]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    timeout-minutes: 10
 
     steps:
       - name: Checkout repository
@@ -32,8 +40,7 @@ jobs:
           source ./venv/bin/activate
           echo "PATH=${PATH}" >> "${GITHUB_ENV}"
           python -m pip install --upgrade pip
-          python -m pip install --requirement development-requirements.txt
-          python -m pip install --requirement requirements.txt
+          python -m pip install --group all .
 
       - name: Analysing the code with pylint
         run: |
diff --git a/.github/workflows/spellcheck.yaml b/.github/workflows/spellcheck.yaml
@@ -1,9 +1,13 @@
-name: spellcheck
+name: Spellcheck
 
 on:
   pull_request:
     branches: [main]
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
 permissions: {}
 
 jobs:
diff --git a/.vscode/cspell.json b/.vscode/cspell.json
@@ -2,26 +2,44 @@
   "version": "0.2",
   "language": "en",
   "words": [
+    "analysing",
+    "applehelp",
+    "autodoc",
+    "autodocsumm",
+    "bugtracker",
     "CCLA",
     "CODEOWNER",
+    "cooldown",
+    "devhelp",
+    "dowjones",
     "EFEAT",
+    "esbenp",
     "GROUPID",
+    "htmlhelp",
     "ICLA",
     "IJIC",
-    "Senzing",
-    "WATCHLIST",
-    "analysing",
-    "dowjones",
-    "esbenp",
     "isort",
+    "jquery",
+    "jsmath",
     "kwargs",
     "mypy",
+    "psutil",
     "pylint",
+    "pylintrc",
     "pytest",
+    "qthelp",
+    "remoteliteralinclude",
+    "Senzing",
+    "serializinghtml",
     "setuptools",
     "shellcheck",
+    "sphinxcontrib",
+    "sphinxext",
     "stackoverflow",
-    "venv"
+    "typehints",
+    "venv",
+    "virtualenv",
+    "WATCHLIST"
   ],
   "ignorePaths": [
     ".git/**",
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,12 +2,15 @@
 
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-[markdownlint](https://dlaa.me/markdownlint/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+The changelog format is based on [Keep a Changelog] and [CommonMark].
+This project adheres to [Semantic Versioning].
 
 ## [1.0.0] - yyyy-mm-dd
 
 ### Added to 1.0.0
 
 - ...
+
+[CommonMark]: https://commonmark.org/
+[Keep a Changelog]: https://keepachangelog.com/
+[Semantic Versioning]: https://semver.org/
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,46 +1,97 @@
-# Contributor Covenant Code of Conduct
+# Contributor Covenant 3.0 Code of Conduct
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We pledge to make our community welcoming, safe, and equitable for all.
 
-## Our Standards
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals,
+regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability,
+sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin,
+socio-economic position, level of education, or other status.
+The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
 
-Examples of behavior that contributes to creating a positive environment include:
+## Encouraged Behaviors
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior.
+We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
 
-Examples of unacceptable behavior by participants include:
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
 
-## Our Responsibilities
+## Restricted Behaviors
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone's personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
 
-## Scope
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate.
+Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly.
+To report a possible violation, contact the project team at <support@senzing.com>
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner.
+They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants.
+Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality.
+In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
 
-## Enforcement
+## Addressing and Repairing Harm
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@senzing.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole.
+Depending on the severity of a violation, lower rungs on the ladder may be skipped.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3. Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces.
+Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
+Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources).
+The enforcement ladder was inspired by the work of [Mozilla's code of conduct team](https://github.com/mozilla/inclusion).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
diff --git a/SECURITY.md b/SECURITY.md
diff --git a/development-requirements.txt b/development-requirements.txt
diff --git a/documentation-requirements.txt b/documentation-requirements.txt
diff --git a/pyproject.toml b/pyproject.toml
diff --git a/requirements.txt b/requirements.txt

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+# Senzing`
	`2`	`+`
	`3`	`+- Perform the steps specified by <https://raw.githubusercontent.com/senzing-factory/claude/refs/tags/v1/commands/senzing.md>`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`- # Default code owner`
	`1`	`+# Default code owner`
`2`	`2`
`3`	`3`	`* @Senzing/senzing-mappers`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-name: add labels standardized`
	`1`	`+name: Add labels standardized`
`2`	`2`
`3`	`3`	`on:`
`4`	`4`	`issues:`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-name: add to project senzing github organization dependabot`
	`1`	`+name: Add to project senzing github organization dependabot`
`2`	`2`
`3`	`3`	`on:`
`4`	`4`	`pull_request:`