2.0 Tracking

[Kircheneer]

I think we should get the following things over the line in preparation for 2.0:

• Simplify model interface #231 (if we want to do it)
• Type hinting overhaul. #219
• Thinking about further necessary breaking changes
• Better discoverability of external API #228 (including any changes made in other items)
• Empty DiffSync instance evaluates as false #84
• diffsync.DiffSync naming #233
• Pydantic 2.0

[jamesharr]

Thoughts on bumping to Pydantic v2?

It's not 100% backwards compatible, but they did improve performance a decent amount. Some libraries like Beanie will support both v1 and v2 and it might actually be the case that diffsync can support both.

If no one else is doing it, I might spend a little bit of time POC'ing a bump

[Kircheneer]

Do check out the [next-2.0] branch - Pydantic 2.0 is already in 🎉 develop...next-2.0

[Kircheneer]

FYI: We will merge #114 before cutting the release but the other changes will be postponed in favor of getting Pydantic 2.0 support out there sooner rather than later.

[jdrew82]

Closing as we're on version 2.0 now and the original concerns have their own Issues or have been addressed.