potiuk commented on issue #32311: URL: https://github.com/apache/airflow/issues/32311#issuecomment-1707780110
> Would upgrading to pydantic 2 break core Airflow functionality? I have sometimes updated other packages (pandas, pyarrow) beyond the constraints Airflow sets. The latest release of polars depends on pydantic 2.0 but I can't break Airflow over my eagerness to update. As @uranusjr wrote - no, it should not break anything once you use 2.7.1. In 2.7.0 you will have warnings about some deprecated Pydantic features, but it should be harmless otherwise. In 2.7.1 you should get the warnings suppressed. 2.8.0 will likely require you to use Pydantic 2. We are not yet "actively" using Pydantic, it's mostly in-development support. It also allows you to serialize Pydantic models (if for example you pass them as XComs) but I think upcoming 2.7.1 should generally make them work for both Pydantic 1 and 2. If you are not passing Pydantic models this way - you should be generally unaffected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
