Require jsonpointer>=3.2

[stefankoegl]

Raises the jsonpointer requirement in requirements.txt (which setup.py reads for install_requires) from >=1.9 to >=3.2.

Why

• The BUG: JSON Patch operations sometimes treat strings as arrays (RFC 6902 non-compliant) #178 fix can't be tested in CI as things stand. jsonpointer 3.2 no longer resolves pointers into strings, which is what BUG: JSON Patch operations sometimes treat strings as arrays (RFC 6902 non-compliant) #178 requires. With older versions, the _to_last helper added in Prevent RFC 6901 pointer indexing into strings #196 is what rejects them. CI always installs the latest jsonpointer, so the helper never runs in CI: the code from before Prevent RFC 6901 pointer indexing into strings #196 passes StringIndexingTests on jsonpointer 3.2 too. Requiring 3.2 makes the tested configuration the only supported one.
• >=1.9 is already inaccurate. tests.py only passes in full from jsonpointer 1.14 on. With 1.9–1.13, a patch with "path": null raises AttributeError instead of InvalidJsonPatch (test_path_with_null_value).

No Python version is dropped: jsonpointer 3.2 requires Python ≥ 3.10, the same as jsonpatch's python_requires.

With 3.2 required, the _to_last helper is redundant. This PR leaves it in place; it can be removed separately if wanted.

Verification

• Installing the package pulls in jsonpointer 3.2.0. Its metadata declares jsonpointer>=3.2, and asking for jsonpointer==3.1.1 alongside it fails as unsatisfiable.
• python tests.py passes with jsonpointer 3.2.0.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JqGXptMsaz9bfrMoaMpZ1A

---

Generated by Claude Code