Summary
Follow-up from #1419 audit: decide whether and when to remove the deprecated public GFQL validation API surface.
This is a public API / compatibility decision, not a narrow deletion worker lane.
Audit finding
Current pygraphistry master inspected at 8b83f8db:
graphistry/compute/gfql/validate.py is deprecated but still ~684 LOC.
- It is re-exported from:
graphistry.compute.gfql
graphistry.compute.gfql_validation
- Tests still import and pin it:
graphistry/tests/compute/test_validate.py
graphistry/tests/compute/test_gfql_validation.py
- Removing it would be a user-facing API break, not just internal cleanup.
Scope
- Decide policy:
- keep indefinitely,
- warn harder and schedule removal,
- move behind compatibility package,
- or delete in next major release.
- If removal is approved, define the release/version gate and migration note.
- Only then file a code deletion PR.
Done when
Related
Summary
Follow-up from #1419 audit: decide whether and when to remove the deprecated public GFQL validation API surface.
This is a public API / compatibility decision, not a narrow deletion worker lane.
Audit finding
Current pygraphistry master inspected at
8b83f8db:graphistry/compute/gfql/validate.pyis deprecated but still ~684 LOC.graphistry.compute.gfqlgraphistry.compute.gfql_validationgraphistry/tests/compute/test_validate.pygraphistry/tests/compute/test_gfql_validation.pyScope
Done when
Related