3 ms·

Is the complaint that v1 and v2 are different? Why are you learning v1 at all?

• behnamoh 3y ago
  I'm not learning v1. I'm complaining about the constant deprecation of things that already worked. If it's working, why change it? I get that major transitions are difficult, but there are also numerous small deprecations. Nov. 2023 was 2-3 months ago. Yet, code written then throws deprecation warnings now...
  • inspector14 3y ago
    I spent the last month or so migrating over a hundred models to v2 and it has been a pretty pleasant experience. Free performance gains and a lot more clear/readable models. On top of this interacting with complex nested root models is now much more organized and `.model_validate(data).model_dump()` always works whereas before I had to do a lot of strange json loading and dumping surrounding instantiation for certain models. The changes are overall good and the library has matured into something that seems like it will be stable for a long time to come. Spend an hour with this https://www.youtube.com/watch?v=ok8bF8M7gjk https://www.youtube.com/watch?v=ok8bF8M7gjk and never look back. Also https://www.youtube.com/watch?v=4yUXPZGhIX8 https://www.youtube.com/watch?v=4yUXPZGhIX8 specifically for migrating from v1 to v2.
  • scolvin 3y ago
    We've had one very small change within V2, related solely to typing. I think you're overblowing this.