Zipper Tools

Pydantic Migration Guides

Why configured @validate_arguments needs manual review in Pydantic v2

Configured validate_arguments decorators are outside the current deterministic migration subset.

Start here

The safe first move

Keep configured @validate_arguments decorators in manual review. The replacement depends on the decorator options and call-site behavior.

Stop before automation when: Decorator config options that change runtime behavior. Wrapped or aliased decorator usage.

Target shape

# manual review required
# configured validate_arguments decorators are outside the supported subset

Repo fit check

Want to know if your repo has this pattern?

Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.

  • Local scan; no repository upload.
  • Supported findings are separated from manual-review findings.
  • Buy only when the repeated pattern is worth automating.
Run the Pydantic scan first View example report See when to buy 
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewable

Why this page exists

Why configured @validate_arguments needs manual review in Pydantic v2

Bare validate_arguments is a clean rename. Configured validate_arguments is not.

Direct answer

What changes

Keep configured @validate_arguments decorators in manual review. The replacement depends on the decorator options and call-site behavior.

Example

Before and after

Before

from pydantic import validate_arguments

@validate_arguments(config={"arbitrary_types_allowed": True})
def create_user(user) -> None:
    ...

After

# manual review required
# configured validate_arguments decorators are outside the supported subset

Decision path

If this repeats across the repo, open the evaluation pages next.

The cleanup pack is strongest when the repo still uses direct pydantic imports and a clean validator/settings/config subset.

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • If the scan output is ambiguous, review its findings and upstream guidance. Do not buy expecting unsupported cases to be resolved.

Typical symptoms

  • The repo already moved beyond bare validate_arguments usage.
  • Teams want the porter to distinguish easy decorator renames from the harder cases.
  • Reviewers need an explicit report entry for configured decorator usage.

What the product covers

  • Explicit unsupported-validate-arguments findings for configured decorators.
  • Cross-links to the supported bare validate_arguments page.
  • Repo-fit guidance before buying the porter.

Manual-review boundary

  • Decorator config options that change runtime behavior.
  • Wrapped or aliased decorator usage.
  • Files bundled with unsupported validator signatures or config migrations.

Keep the migration narrow

Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.

FAQ

Fast answers before you decide

What is the safest fix for validate_arguments kwargs pydantic v2?

Keep configured @validate_arguments decorators in manual review. The replacement depends on the decorator options and call-site behavior.

Can validate_arguments kwargs pydantic v2 be automated?

Automate only the supported subset: Explicit unsupported-validate-arguments findings for configured decorators. Cross-links to the supported bare validate_arguments page. Repo-fit guidance before buying the porter. Keep these cases in manual review: Decorator config options that change runtime behavior. Wrapped or aliased decorator usage. Files bundled with unsupported validator signatures or config migrations.

When should I buy Pydantic v1 to v2 Migration Cleanup Pack?

Use Pydantic v1 to v2 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.

Purchase fit

Choose the lowest-risk next step.

One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.

Buy if

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • The team accepts manual-review findings for alias-heavy imports and signature-heavy validators.

What the workflow includes

  • Installable local CLI workflow, not a hosted black box.
  • Supported validator, settings, import, and config rewrites.
  • Demo report, public proof, coverage notes, rollback checklist, and buyer terms.

Before checkout

  • Stripe Checkout handles secure payment and receipts.
  • Download your purchased ZIP after payment.
  • Runs locally; no hosted API, repo upload, or production credentials needed.
  • The free report includes the evidence needed to evaluate fit. Paid summary and template add-ons are optional.
  • 14-day refund review for published-scope or delivery mismatches.
Run the Pydantic scan first

Explore the details