PR Change Summary

Allowed configuration and base classes to be specified together in thecreate_model() function, addressing a previously raised issue.

• Enabled the use of both__config__ and__base__ increate_model()
• Removed outdated error handling example related tocreate_model configuration
• Updated documentation to reflect the new functionality

Modified Files

• docs/errors/usage_errors.md

Deploying pydantic-docs with    Cloudflare Pages

View logs

CodSpeed Performance Report

Merging#11714 willnot alter performance

_{Comparingcreate-model-config-base (7a702a7) withmain (04fd639)}

Summary

✅ 46 untouched benchmarks

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
pydantic
main.py
Project Total

This report was generated bypython-coverage-comment-action

How does that config merge with the explicitly set config?

It will be equivalent to the following, as shown in the added test:

classBase(BaseModel):a:strmodel_config= {'str_to_lower':True}classModel(Base):model_config= {'str_max_length':3}

Which will result inModel having both configuration values.create_model() is in fact completely equivalent to normal subclassing, just that it is meant to be dynamic.

(e.g. can this do weird things like make the parent model fields all strict?)

as in "normal" subclassing, this shouldn't be the case.