nate nowack

thanks for the issue @tekumara - this is related to our ongoing migration/compatibility layer between pydantic 1 and 2. are there specific warnings you think should be filtered out?

hi @ori-scala - we're planning on getting fully over to pydantic 2 in June of this year.

closed by https://github.com/PrefectHQ/prefect/pull/14894

hi @bjorhn - i can take a look at adding a test here for this, since yes this is something we should probably have a sanity check unit test for

@desertaxle I added a test here

hi @thundercat1 - I think this issue has mostly to do with the fact that you cannot pickle a `_thread.RLock` object in general ```python import pickle import threading def minimal_repro():...

hi @qiangxinglin - thank you for the issue! we are definitely interested in improving import times wherever we can (cc @aaazzam) > I want to do similar things as in...

chatted sync already but lgtm besides the filter (i think we should update the tests instead)

> > maybe we could add a test for the deprecation warning case? and just out of curiosity, why FutureWarning instead of DeprecationWarning? > > @zzstoatzz I will add a...

hi @li-dennis - i can reproduce this, thank you for the issue! we'll get this looked at can you share your version of `pydantic` please?