Julio C. Galindo
Julio C. Galindo
@vector-of-bool, @CaseyCarter, @Quincunx271, @AnotherFoxGuy can you check the commit please?
@tiangolo @alejsdev or some other maintainer... could you please review this issue?
@svlandeg Nice to hear you are taking action on this matter. There is remark, the parameter the was renamed between Pydantic v1 and v2 is `regex`-> `pattern`, not as listed...
Hi @YuriiMotov, nice to hear from you again. Sorry for not have given a better description for the problem, but here it is: ```python from sqlmodel import SQLModel, Field class...
Noted @YuriiMotov, I will do that. [Here](https://docs.pydantic.dev/latest/errors/usage_errors/#removed-kwargs) there is the reference to the removed parameter and error raise associated to it. [Here](https://github.com/pydantic/pydantic/blob/5a6ff49a6e7f9c6517994d99d7ace77ad8e3fb53/pydantic/fields.py#L1242) is its implementation. I would like to propose...
> I think this should be done in a separate PR. And I would do it in a different way - I would add `pydantic_kwargs` and `json_schema_extra` parameters and deprecate...
> I still can't get it.. Could you please share a code example that works in current version (0.0.24) but will be broken after applying changes from this PR? No,...
> So, it's not breaking. Breaking changes is when new changes brake old user's code that worked without errors previously Noted! Thanks
This is fixed in #1603
@YuriiMotov Hi again! Maybe take a look at this, this is also related with Python 3.14 support and `pydantic>=2.12` update.