Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

chore: deprecate document.execute() in favor of generate() (v0.19.0)

Summary

Aligns the Python SDK with vlm-lab PR #1595 which removes the /document/execute endpoint and unifies redaction domains under /document/generate.

The execute() method on FilePredictions (used by client.document, client.audio, client.video) is now a thin deprecation wrapper that:

  1. Emits a DeprecationWarning
  2. Converts the name param from slash to dot notation (healthcare/phi-redactionhealthcare.phi-redaction)
  3. Delegates to self.generate() with the converted domain

No new functionality — this is purely a deprecation shim.

Review & Testing Checklist for Human

  • FilePredictions is shared across document, audio, and video routes. Verify that audio.execute() and video.execute() are also intended to be deprecated, or if only document.execute() should be affected. The current change deprecates ALL routes.
  • The version parameter is silently dropped — the old execute() sent version to the API; the new delegation to generate() does not forward it. Confirm this is acceptable.
  • The model parameter defaults to "vlm-1" in generate() — old execute() never sent a model field. Verify the backend handles this correctly for former execute use cases.
  • Run make test to confirm existing tests pass (especially test_document_execute in tests/test_predictions.py), since the mock expectations may have changed.

Notes

…v0.19.0)

- Add deprecation warning to execute() method
- Redirect execute() calls to generate() with domain name conversion (slash -> dot)
- /document/execute endpoint removed in v0.19.0, redaction domains now use /document/generate

Co-Authored-By: dinesh@vlm.run <dinesh@vlm.run>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants