Deprecated pydantic config #117

Activity

1. TheJedinator commented on Sep 8, 2025

   

   TheJedinator

   on Sep 8, 2025

   More actions

   Since per your contribution guidelines you suggest opening a discussion and @jekozyra has done so I'll leave the very minimal change required for you to stop having warnings pushed to all pydantic v2 customers.

   class UniversalBaseModel(pydantic.BaseModel):
       class Config:
           # note smart_union has been removed here as it's now the default in pydantic v2
           populate_by_name = True
           validate_by_name = True # formerly allow_population_by_field_name
           json_encoders = {dt.datetime: serialize_datetime}
           # Allow fields beginning with `model_` to be used in the model
           protected_namespaces = ()
   

   👍React with 👍12Reacted by Zaeem, Michael "Mike" Churilov, Keaton Neville, Nate Halsey, Jake Proctor, Cameron Gorrie, Benjamin Gee, Simon Helsen, Kent Ma, Alexander Prams and 2 more
2. TheJedinator commented on Sep 8, 2025

   

   TheJedinator

   on Sep 8, 2025

   More actions

   More info about pydantic unions can be found here: https://docs.pydantic.dev/latest/concepts/unions/
3. aprams commented on Nov 27, 2025

   

   aprams

   on Nov 27, 2025

   More actions

   We would also appreciate this! Polluting our logs currently

   👍React with 👍1Reacted by Carlos de la Torre

   👀React with 👀1Reacted by darmen-engineering
4. cmdelatorre commented on Dec 9, 2025

   

   cmdelatorre

   on Dec 9, 2025

   More actions

   Same here. We'd greatly appreciate it if this could be updated.
5. sidmitra commented on Apr 21, 2026

   

   sidmitra

   on Apr 21, 2026

   Last edited by sidmitra

   More actions

   Note that pydantic.v1 stuff might be holding up other upgrades. I believe pydantic.v1 isn't officially supported on python 3.14+

   pydantic/pydantic#12618

   When a module is imported from pydantic.v1 and a user is running Python 3.14, they'll get a warning: "Core Pydantic V1 functionality isn't compatible with Python 3.14 or greater."

   It might be ok to pin to pydantic v2 or do conditional import based logic to do different things if pydantic v2 or v1 was found(for backward compatability). Otherwise mostly it means we'd have to pin to a temporary git fork till this is resolved here.

   PS: I can send a PR if needed.
6. darmen-engineering commented on May 7, 2026

   

   darmen-engineering

   on May 7, 2026

   More actions

   We would also appreciate this! Polluting our logs currently

   Same here! @aprams Polluting our logs too.
7. darmen-engineering commented on May 18, 2026

   

   darmen-engineering

   on May 18, 2026

   More actions

   PS: I can send a PR if needed.

   @sidmitra have you sent one? Looking forward to it :)
8. niteshsandal-merge

   added a commit that references this issue on Jul 17, 2026

   Add regression test for pydantic config deprecation warnings (#117)

   ...

   47dbd6c